How to resolve Node.js: "Error: ENOENT: no such file or directory"

Question

I have a Node.js web application currently running on a server successfully. Now I'm trying to set up a local copy on my development server.

I currently have Node.js, NPM and MongoDB Installed just like what I have in production server. However, the error below occurs when I try to start the Node.js server.

What could be causing this issue?

cd ~/node/nodeapp
node app.js

Output:

fs.js:640
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open '/home/embah/node/nodeapp/config/c
onfig.json'
    at Error (native)
    at Object.fs.openSync (fs.js:640:18)
    at Object.fs.readFileSync (fs.js:508:33)
    at Object.<anonymous> (/home/embah/node/nodeapp/config/config.js:4:28)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/home/embah/node/glorby/app.js:13:16)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:509:3

It's complaining about a missing file. Do you have "/home/embah/node/nodeapp/config/c onfig.json" in the correct location in your system? — TeaCoder, Apr 06 '17 at 16:23

Trott · Accepted Answer · 2017-07-23T01:09:35.230

97

Your app is expecting to find a file at /home/embah/node/nodeapp/config/config.json but that file does not exist (which is what ENOENT means). So you either need to create the expected directory structure or else configure your application such that it looks in the correct directory for config.json.

edited Jul 23 '17 at 01:09

answered Apr 06 '17 at 16:23

Trott

66,479
23
173
212

score 75 · Answer 2 · answered Jun 16 '18 at 21:15

75

After going through so many links and threads and getting frustrated over and over again, I went to the basics and boom! it helped. I simply did:

npm install

I don't know, but it might help someone :)

answered Jun 16 '18 at 21:15

olleh

1,915
18
21

11

This may work for some, but it doesn't work for me. – lwdthe1 Apr 23 '20 at 03:12
7

Not as simple as my solution--computer rebooted, opened powershell in c:\windows\system, and I didn't realize I wasn't in my project directory! – Michael C. Gates May 05 '20 at 15:02
2

I too faced the same issue & it worked for me too. Could anyone please explain why is it so? I know that npm's searching for some directory which it didn't find, but why? – Abhishek Thakur Sep 22 '20 at 06:05
2

Oddly `npm install` resulted in the same error for a completely new install, but `npm update` worked, then subsequent `npm install` worked too! – Peter Lewis Sep 07 '21 at 09:39
not sure why but this worked for me, maybe you can try this as a first go and if you are lucky you will be done in few instants – mikey Jan 11 '22 at 23:56

score 21 · Answer 3 · edited Dec 31 '22 at 16:46

21

Regarding:

92% additional asset processing scripts-webpack-plugin× ｢wdm｣: Error: ENOENT: no such file or directory, open....

If anyone faced to such an error, you should do followings:

you should check if the file path is correct in the angular.json file.

"scripts": [ "node_modules/jquery/dist/jquery.min.js", "node_modules/bootstrap/dist/js/bootstrap.js" ],
you should press Ctrl + C and rerun the project.

edited Dec 31 '22 at 16:46

Peter Mortensen

30,738
21
105
131

answered Jun 27 '19 at 16:10

Odiljon Djamalov

761
8
11

Better check the path relative to angular.json config file. for me I had to add root folder name as well. "scripts": [ "../MYROOTFOLDER/node_modules/jquery/dist/jquery.min.js", "../MYROOTFOLDER/node_modules/bootstrap/dist/js/bootstrap.js" ], – Yergalem Oct 02 '19 at 02:13

score 20 · Answer 4 · edited Dec 31 '22 at 16:43

20

olleh's answer worked, because npm install will create a node_modules directory in the current path where it is executed. So, while using the file server system module, the below declaration locate files from the top level directory of node_modules.

const fs = require('fs')

edited Dec 31 '22 at 16:43

Peter Mortensen

30,738
21
105
131

answered May 07 '19 at 23:27

Aniruddha Pandey

428
6
9

score 14 · Answer 5 · answered Jun 15 '20 at 22:55

In my case the issue was caused by using a file path starting at the directory where the script was executing rather than at the root of the project.

My directory stucture was like this: projectfolder/ ├── package.json ├── scriptFolder/ │ ├── myScript.js

And I was calling fs.createReadStream('users.csv') instead of the correct fs.createReadStream('scriptFolder/users.csv')

score 10 · Answer 6 · edited Dec 31 '22 at 17:13

If you have the same error while using Express.js in your project this worked for me:

In my project, when I ran an Express.js application, I noticed that the current working directory was the root directory of the project (while I was trying to read a file that was located in the script's directory). It could not run the file since process.cwd() !== __dirname.

You can check it out and console log process.cwd() in the script you are trying to read the JSON file with.

I just changed the path to:

const fs = require('fs');
fs.readFileSync(`${__dirname}\\FILENAME`);

score 6 · Answer 7 · edited Dec 31 '22 at 16:38

6

I also had this issue, because I had another console window open that was running the application and I was attempting to rerun yarn start in another console window.

The first Yarn executing prevented the second from writing. So I just killed the first process and it worked.

edited Dec 31 '22 at 16:38

Peter Mortensen

30,738
21
105
131

answered May 15 '18 at 08:24

Damian Green

6,895
2
31
43

1

Had this exact issue because of an issue with VS Code – Jonathan van de Veen Sep 11 '19 at 08:02

score 6 · Answer 8 · edited Dec 31 '22 at 16:54

6

I solved this error by simply creating a blank file at that location for which I got the error. If you are getting the error for a directory, you can try by also creating an empty directory.

edited Dec 31 '22 at 16:54

Peter Mortensen

30,738
21
105
131

answered Jun 13 '20 at 17:58

sanghamitra Ravi Kant

71
1
1

Analyst · Answer 9 · 2023-01-02T13:51:07.103

6

I was facing this issue with ng-package.json file, while creating a plugin. I found out I was providing the wrong path in angular.json. Fixed my file path, issue was resolved.

May be helpful for someone.

edited Jan 02 '23 at 13:51

answered Mar 24 '21 at 10:06

Analyst

751
6
15

score 5 · Answer 10 · edited Dec 31 '22 at 16:50

5

In my case, the issue occurred after I switched from a Git branch to another, references to some old files remained in the scripts inside the "node_modules/.cache" directory.

Deleting the "node_modules", "build" directories and "package-lock.json" file and then issuing the "npm install" command has fixed the issue for me.

edited Dec 31 '22 at 16:50

Peter Mortensen

30,738
21
105
131

answered May 18 '20 at 12:29

Hasnaa Ibraheem

1,132
1
10
18

1

Thank you. Deleting the package-lock.json file and then running "npm install" helped solve my issue. My project had a local project dependency and I had recently deleted that second project's folder then re-cloned the repository. – Bryce Siedschlaw Jun 09 '20 at 13:03

score 5 · Answer 11 · edited Dec 31 '22 at 16:55

5

If there isn't any layout folder, just use it like this in your routing:

app.get('/', (req, res) => {
    res.render('something', { layout: false });
})

Here change something with your folder name.

edited Dec 31 '22 at 16:55

Peter Mortensen

30,738
21
105
131

answered Jun 27 '20 at 06:10

MD.FAHIM HOSSEN

90
2
10

score 3 · Answer 12 · edited Dec 31 '22 at 17:04

Make sure your angular.json file has the "style" and "scripts" array as below (for Angular 12 and above):

"styles": [
          "src/styles.css",
          "./node_modules/bootstrap/dist/css/bootstrap.css"
        ],
"scripts": [
          "node_modules/jquery/dist/jquery.min.js",
          "node_modules/bootstrap/dist/js/bootstrap.js"
        ]

Once this is done, press Ctrl + C and then ng serve.

score 3 · Answer 13 · edited Dec 31 '22 at 17:08

3

I don't know if anyone would see this, but I'll say my answer.

First you need to be in the app directory that you created with the following command:

npx create-react-app [app-name]

Next run:

sudo npm install

to make it install all dependencies from

package.json

Then run:

sudo npm start

and make sure to run them with the sudo command, because sometimes it is absolutely necessary.

edited Dec 31 '22 at 17:08

Peter Mortensen

30,738
21
105
131

answered Dec 05 '21 at 18:23

Javad

213
2
9

I was fighting through an issue with it not being able to write to `/private/var/folders` on mac. Ran it sudo, and it worked... Thanks. – Jake Jan 29 '22 at 18:22

score 2 · Answer 14 · edited Dec 31 '22 at 17:12

2

This is a helpful link on the multer GitHub page.

But for me, I also have to create a public folder in the server folder. It's like -cb(null,'public/').

edited Dec 31 '22 at 17:12

Peter Mortensen

30,738
21
105
131

answered Dec 28 '20 at 19:46

BUGATTI AJAY

759
6
3

score 1 · Answer 15 · edited Dec 31 '22 at 16:56

1

I added the PM2_HOME environment variable on the system level and now it works all right.

edited Dec 31 '22 at 16:56

Peter Mortensen

30,738
21
105
131

answered Nov 02 '20 at 15:27

kepy97

988
10
12

Can you [elaborate](https://stackoverflow.com/posts/64648421/edit) in your answer, e.g., by adding some references? (But ***** ***without*** ***** "Edit:", "Update:", or similar - the answer should appear as if it was written today). – Peter Mortensen Dec 31 '22 at 16:57

score 1 · Answer 16 · edited Dec 31 '22 at 17:06

1

If you're coding with TypeScript, remember that the transpiled-JS folder is where JavaScript would be searching for your file and will definitely not be able to find your html-file; hence such error.

Therefore, you'd need to copy the file into the transpiledJS folder for it to be located.

edited Dec 31 '22 at 17:06

Peter Mortensen

30,738
21
105
131

answered Nov 15 '21 at 13:30

Chukwunazaekpere

906
1
6
13

score 1 · Answer 17 · edited Dec 31 '22 at 17:25

Sometimes you see this issue in the following scenario.

Let's assume that you have a folder structure like node-projects (folder) → my-blog (folder) → my-blog (folder where the actual project exists), but you are in the my-blog directly, and it is an immediate child of node-project. Try to run your command in that directory.

As the project is present in my-blog that is an immediate child of my-blog. So, in this case, it searches your config.json file in my-blog (which is an immediate child of node-projects) rather than finding the config.json file in my-blog that is an immediate child of my-blog.

Just transfer your directory by hitting the command cd my-blog in your terminal and that's it. The problem is resolved!

score 0 · Answer 18 · answered Apr 24 '19 at 13:40

0

In my case

import { Object } from '../config/env';

gave me the error.

I solved it with change the address like this:

import { Object } from './../config/env';

answered Apr 24 '19 at 13:40

msalihbindak

592
6
21

score 0 · Answer 19 · edited Dec 31 '22 at 16:47

0

Running

npm run scss
npm run start

in that order in the terminal solved the issue for me.

edited Dec 31 '22 at 16:47

Peter Mortensen

30,738
21
105
131

answered Mar 11 '20 at 11:44

Onat Korucu

992
11
13

1

It would be helpful if you provided some information about what those commands do (or are supposed to do). – Jeff Wright Nov 06 '21 at 19:22

TimJ0212 · Answer 20 · 2023-01-01T18:03:06.197

0

I work with Visual Studio Code, Git and Nx and often have the problem that Visual Studio Code performs an auto staging.

In combination with Nx, it comes very often to problems. Simply unstaging the files in Visual Studio Code often helps.

edited Jan 01 '23 at 18:03

answered Feb 25 '22 at 12:36

TimJ0212

11
1
2

What is "nrwl"? Isn't it the short name of the company (Narwhal Technologies)? Do you mean Nx, Nx Cloud, or Nx Console? – Peter Mortensen Dec 31 '22 at 17:20

score 0 · Answer 21 · answered Apr 25 '22 at 14:59

0

Weirdly, in my project, I always get this error first time I add/remove a package, but then I run the same command again and it works on the second run.

answered Apr 25 '22 at 14:59

Michal Kurz

1,592
13
41

score 0 · Answer 22 · edited Dec 31 '22 at 17:23

0

I had this error while uninstalling Bootstrap from the project, so I just deleted the script and style from file angular.json.

"styles": [
              "node_modules/bootstrap/dist/css/bootstrap.min.css"
            ],
 "scripts": [
              "node_modules/jquery/dist/jquery.min.js"
          ]

Cleared this to

"styles"  : [    ],
"scripts" : [    ]

This solved my issue.

edited Dec 31 '22 at 17:23

Peter Mortensen

30,738
21
105
131

answered Jul 19 '22 at 06:38

saurabh solanke

19
1
5

score 0 · Answer 23 · answered Oct 11 '22 at 04:58

0

My mistake was not adding / before the path. Correct path: /Users/mee/Documents/file_name.jpg

answered Oct 11 '22 at 04:58

GorvGoyl

42,508
29
229
225

score 0 · Answer 24 · answered Jun 18 '23 at 19:21

0

for me running

npm cache verify

indicated that some file is corrupted and run the following command

sudo chown -R 501:20 "/Users/Mac/.npm"

did the trick. I assume the 2nd command will be your PC specific.

answered Jun 18 '23 at 19:21

tk_tanz

384
2
7

score 0 · Answer 25 · edited Jul 15 '23 at 10:48

0

Use __dirname:

const string = fs.readFileSync(__dirname + "/file.json", "utf8");

edited Jul 15 '23 at 10:48

Tyler2P

2,324
26
22
31

answered Jul 13 '23 at 12:19

KISHORE K J

186
2
4

score -1 · Answer 26 · edited Dec 31 '22 at 16:41

-1

It’s happened with me. I deleted some CSS files by mistake and then copied back. This error appeared at that time. So I restarted all my Docker images and other servers and then it went away.

edited Dec 31 '22 at 16:41

Peter Mortensen

30,738
21
105
131

answered Apr 03 '19 at 11:35

Yasir Akbar

25
1

score -1 · Answer 27 · edited Dec 31 '22 at 16:52

-1

I tried something and got this error:

Error: ENOENT: no such file or directory, open 'D:\Website\Nodemailer\Nodemailer-application\views\layouts\main.handlebars'

The fix I got was to literally construct the directory as it is seen. This means labeling the items exactly as shown. It is weird that I gave the computer what it wanted.

edited Dec 31 '22 at 16:52

Peter Mortensen

30,738
21
105
131

answered May 25 '20 at 19:53

Blank456

21

2

Instead of "I tried something", can you explain what you were doing? There are a lot of examples in the answers already. If yours is truly unique, try to explain why, so that it can stand out to someone looking for your answer among the others. – ptpaterson May 26 '20 at 04:41

How to resolve Node.js: "Error: ENOENT: no such file or directory"

27 Answers27

Linked