Ошибка enoent no such file or directory

Update:

I think in my case it happened because the project was initially installed with pnpm, and I ran yarn add thereafter.

Hitting this error consistently today.

Both locally on MacOS and on Ubuntu in CI: https://github.com/akd-io/create-next-stack/actions/runs/4772052085/jobs/8484361470?pr=172

local yarn-error.log:

Arguments: 
  /Users/akd/.nvm/versions/node/v18.13.0/bin/node /Users/akd/.nvm/versions/node/v18.13.0/bin/yarn add @emotion/react@^11.0.0 @emotion/styled@^11.0.0 @chakra-ui/icons@^2.0.0 @chakra-ui/react@^2.0.0 @mui/material@^5.0.0 react-hook-form@^7.0.0 formik@^2.0.0 framer-motion@^9.0.0 mrm@^4.0.0 mrm-task-lint-staged@^7.0.0

PATH: 
  /Users/akd/workspace/create-next-stack/packages/create-next-stack/node_modules/.bin:/Users/akd/Library/pnpm/global/5/.pnpm/pnpm@8.3.0/node_modules/pnpm/dist/node-gyp-bin:/Users/akd/workspace/create-next-stack/node_modules/.bin:/Users/akd/Library/pnpm:/opt/homebrew/opt/openjdk/bin:/Users/akd/.nvm/versions/node/v18.13.0/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/akd/Library/pnpm:/opt/homebrew/opt/openjdk/bin:/Users/akd/.nvm/versions/node/v18.13.0/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Users/akd/.yarn/bin:/Users/akd/.yarn/bin:/Users/akd/.nvm/versions/node/v18.13.0/bin

Yarn version: 
  1.22.19

Node version: 
  18.13.0

Platform: 
  darwin arm64

Trace: 
  Error: ENOENT: no such file or directory, copyfile '/Users/akd/Library/Caches/Yarn/v6/npm-globby-11.1.0-bd4be98bb042f83d796f7e3811991fbe82a0d34b-integrity/node_modules/globby/index.js' -> '/Users/akd/workspace/create-next-stack-tests/run-d4eb6dcc-9846-4222-a5ef-100d98053b1e/node_modules/@typescript-eslint/typescript-estree/node_modules/globby/index.js'

npm manifest: 
  {
    "name": "run-d4eb6dcc-9846-4222-a5ef-100d98053b1e",
    "version": "0.1.0",
    "private": true,
    "scripts": {
      "dev": "next dev",
      "build": "next build",
      "start": "next start",
      "lint": "next lint"
    },
    "dependencies": {
      "@types/node": "18.15.13",
      "@types/react": "18.0.38",
      "@types/react-dom": "18.0.11",
      "eslint": "8.39.0",
      "eslint-config-next": "13.3.1",
      "next": "13.3.1",
      "react": "18.2.0",
      "react-dom": "18.2.0",
      "typescript": "5.0.4"
    }
  }

yarn manifest: 
  No manifest

Lockfile: 
  No lockfile

In this tutorial, we will help you to resolve the Error: ENOENT: no such file or directory, open
'student.json' issue.

Q: What is fs module in Nodejs?
Ans:

Node.js provides an inbuilt component called FS (File System). The Node. js file system module enables
us to interact with our computer’s file system.

Error: ENOENT: no such file or directory

Error: ENOENT: no such file or directory, open 'student.json'
    at Object.openSync (node:fs:585:3)
    at Object.readFileSync (node:fs:453:35)
    at Object.writeStudentData (D:nodejsfile-examplestudent-service-impl.js:24:21)
    at Object.handler (D:nodejsfile-examplestudent-app.js:10:17)
    at D:nodejsfile-examplenode_modulesyargsbuildindex.cjs:1:8891
    at j (D:nodejsfile-examplenode_modulesyargsbuildindex.cjs:1:4956)
    at M.handleValidationAndGetResult (D:nodejsfile-examplenode_modulesyargsbuildindex.cjs:1:8860)
    at M.applyMiddlewareAndGetResult (D:nodejsfile-examplenode_modulesyargsbuildindex.cjs:1:9502)
    at M.runCommand (D:nodejsfile-examplenode_modulesyargsbuildindex.cjs:1:7231)
    at Xt.[runYargsParserAndExecuteCommands] (D:nodejsfile-examplenode_modulesyargsbuildindex.cjs:1:57762) {
  errno: -4058,
  syscall: 'open',
  code: 'ENOENT',

Follow below steps to resolve Error: ENOENT: no such file or directory, open 'student.json'
issue.

1. This problem occurs when a file does not exist; therefore, check to see if the file exists first.
2. The suitable approach is to use fs.openSync, it
   returns the file descriptor.
3. If the file does not exist, the w flag ensures that it is created, and if it does, it
   is overwritten
   with a new file, overriding its content.
4. If users don’t need the file descriptor, users can close the file by wrapping the call in a
   fs.closeSync() call.

//check if file exist
if (!fs.existsSync('student.json')) {
    //create new file if not exist
    fs.closeSync(fs.openSync('student.json', 'w'));
}

Web development has come a long way now. Instead of using simple HTML/CSS, Javascript and PHP to build websites, developers now can choose from plenty of web development frameworks and server tools that make the job easier. 

In this article, we’re looking at the “enoent: no such file or directory” error when running Node.js web servers, its causes and what you can do to fix the problem.

What causes this error?

As the error message describes, the problem is caused by a missing configuration file or other dependencies required for your website or web app to run properly. 

Other possible causes include the following:

• Incorrect file paths for web server configuration files. 
• NPM configuration folders aren’t made.

Also read: Fix: An unexpected error is keeping you from copying the file

How to fix this?

Here are five fixes you can try out. 

Restart your PC

A quick and simple fix for the problem is to restart your PC. This ensures that any missing processes start up correctly alongside your operating system and that everything is in order before running your project.

Create an NPM directory

One of the main reasons you’d run into this error is that NPM doesn’t have a configuration directory to keep track of your project’s dependencies. 

The simplest way to fix this is to run the npm install command. If that doesn’t work, you can also try running npm update. Running both commands back to back can also sometimes fix the problem. 

Also read: Docs.google.com refused to connect: 6 Fixes

Check your configuration files

Take a good look at the directory that the error message shows. The file at the end is the missing dependency that’s causing this problem. While it can be any of the dependencies in your project, this is often a missing configuration file. 

To resolve the error, you can manually create the mentioned file path with the specified file at the end. Do keep in mind that while it might fix the problem we’re dealing with in this article, it can give you additional errors, as the resulting file will be empty. 

You can then work your way around the new error, if any, by installing any required packages that might be missing from your project. 

Fix the file path

As an extension to the last solution, you can also try and manually fix the file path that the error has reported missing. The specific way to do this varies from framework to framework, so you’ll have to look up the documentation of your specific framework in use to check how to modify file paths.

If you’re sure that the configuration file or dependencies exist, you can manually point your web server to the right file. 

Reinitialise your project

You also might have to reinitialise your project to freshen up all the dependencies you’re using. This can be done by deleting the node_modules folder and the package-lock.json file. Just open a terminal, head over to your project’s root folder and run the following commands one at a time.

rm -rf node_modules package-lock.json
npm install

If you get an error saying you don’t have appropriate permissions to carry out these tasks, prefix sudo to both commands. 

Also read: Fix: Unknown error: soap-error: encoding: object has no uirequestid property