npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\Nuwanst\package.json'

Question

I just want to install socket.io to my project which is located on 3.chat folder. But when I run following command it shows following Warnings.And its not created a node_modules directory inside my project folder. How to fix this?

C:\Users\Nuwanst\Documents\NodeJS\3.chat>npm install socket.io
C:\Users\Nuwanst
`-- socket.io@2.0.3

npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\Nuwanst\package.json'
npm WARN Nuwanst No description
npm WARN Nuwanst No repository field.
npm WARN Nuwanst No README data
npm WARN Nuwanst No license field.

make sure you have extracted the zip file correctly – csandreas1 Mar 07 '19 at 14:12 — csandreas1, Mar 07 '19 at 14:12

score 154 · Answer 1 · answered Sep 07 '18 at 12:36

154

If you already have package-lock.json file just delete it and try again.

answered Sep 07 '18 at 12:36

Aravin

5,983
3
37
54

2

Rsynced all my apps from one server to another and package-lock.json was present there. Deleting it from all apps saved my day. – Rehmat Aug 15 '19 at 09:53
1

Don't add this to source control I am guessing? – sean Dec 20 '19 at 18:30
Yes, this file should be added to `.gitignore` file – Aravin Dec 20 '19 at 21:13
17

I don't have package-lock.json. – towry Jun 10 '20 at 03:26
3

This worked for me after deleting the package-lock.json. Now my question is will the package-lock.json be reacreted after running npm instal? @Aravin Because I am in he install process and i am not seeing it creating the the package-lock.json – Dijiflex Jul 11 '20 at 17:10
2

Thanks it was added after the installation – Dijiflex Jul 11 '20 at 17:50
4

it worked for me, but can you explain this solution? – Duc Nguyen Aug 03 '20 at 05:41
1

After 1 hour of fight, your solution worked for me. Thanks! – Régis NIOX Oct 14 '21 at 13:37
Glad to know that @RégisNIOX – Aravin Oct 15 '21 at 10:23

score 135 · Accepted Answer · edited Nov 30 '18 at 13:12

135

Have you created a package.json file? Maybe run this command first again.

C:\Users\Nuwanst\Documents\NodeJS\3.chat>npm init

It creates a package.json file in your folder.

Then run,

C:\Users\Nuwanst\Documents\NodeJS\3.chat>npm install socket.io --save

The --save ensures your module is saved as a dependency in your package.json file.

Let me know if this works.

edited Nov 30 '18 at 13:12

Rusty

7,918
10
50
72

answered Aug 06 '17 at 11:54

Clive Machado

1,487
1
10
15

2

This worked for me. Thanks! Note that when you run "npm init" it will ask you to enter a lot of fields, but the default values are in parenthesis. Just enter through and accept defaults. – VoteCoffee Nov 13 '20 at 16:05
1

Most of the cases this is not the correct answer. Please check @Aravin's answer – Sisir Jun 26 '21 at 10:48

score 13 · Answer 3 · answered Oct 30 '20 at 15:38

13

Make sure you are on the right directory where you have package.json

answered Oct 30 '20 at 15:38

Vasanthan

131
1
2

score 9 · Answer 4 · answered Jul 14 '18 at 14:45

You need to make sure if package.json file exist in app folder. i run into same problem differently but solution would be same

Run this command where "package.json" file exist. even i experience similar problem then i change the folder and got resolve it. for more explanation i run c:\selfPractice> npm start whereas my package.json resides in c:\selfPractice\frontend> then i change the folder and run c:\selfPractice\frontend> npm start and it got run

score 6 · Answer 5 · answered Aug 13 '20 at 23:35

NOTE: if you are experiencing this issue in your CI pipeline, it is usually because npm runs npm ci instead of npm install. npm ci requires an accurate package-lock.json.

To fix this, whenever you are modifying packages in package.json (e.g. moving packages from devDependencies to Dependencies like I was doing) you should regenerate package-lock.json in your repository by running these commands locally, and then push the changes upstream:

rm -rf node_modules
npm install
git commit package-lock.json
git push

score 4 · Answer 6 · edited Oct 23 '19 at 11:54

4

finally, I got a solution if you are getting:-

**npm WARN tar ENOENT: no such file or directory,.......**

then it is no issue of npm or its version it is os permission issue to resolve this you need to use below command:-

sudo chown -R $USER:$USER *

additional

sudo chmod -R 777 *

then run:-

sudo npm i

edited Oct 23 '19 at 11:54

Yaser Darzi

1,415
10
23

answered Oct 23 '19 at 10:05

AAAmresh 007

57
1
1

9

Please don't run `sudo chmod -R 777 *` on your workspace. – Ziv Aug 05 '21 at 08:02

score 2 · Answer 7 · answered Apr 10 '20 at 13:40

2

If your folder already have package.json

Then,

Copy the path of package.json

Open terminal

Write:

cd your_path_to_package.json

Press ENTER

Then Write:

npm install

This worked for me

answered Apr 10 '20 at 13:40

Parth Developer

1,190
11
26

score 1 · Answer 8 · answered Dec 16 '20 at 17:46

1

Delete package.json and package-lock.json file

Then type npm init

after that type npm install socket.io --save

finally type npm install

It works for me

answered Dec 16 '20 at 17:46

Malith Ileperuma

722
8
26

score 1 · Answer 9 · answered Dec 31 '20 at 12:12

If you're trying to npm install on a folder that's being rsync'd from somewhere else, remember to add this to your rsync --exclude

yourpath/node_modules

Otherwise, NPM will try to add node_modules and rsync will remove it immediately, causing many npm WARN enoent ENOENT: no such file or directory, open errors.

score 1 · Answer 10 · answered Jan 22 '21 at 21:26

1

update version in package.json is working for me

answered Jan 22 '21 at 21:26

Che

11
1

score 0 · Answer 11 · answered May 29 '19 at 18:50

if your node_modules got installed in say /home/UserName/ like in my case, your package-lock.json file will also be there. just delete this file, go back to your app folder and run npm init and then npm install <pkgname> (e.g express) and a new node_modules folder will be created for your.

score 0 · Answer 12 · answered Dec 19 '19 at 02:26

0

I had this in a new project on Windows. npm install had created a node_modules folder for me, but it had somehow created the folder without giving me full control over it. I gave myself full control over node_modules and node_modules\.staging and it worked after that.

answered Dec 19 '19 at 02:26

John Fouhy

39,311
19
61
77

What are the steps to give yourself full control? – Aakash Goplani Jul 06 '20 at 14:39
@KinleyChristian right click on the folder, select Properties, then go into the security tab. – John Fouhy Jul 08 '20 at 06:52

score 0 · Answer 13 · answered Aug 02 '20 at 06:17

0

Seems you have installed express in root directory.Copy path of package.json and delete package json file and node_modules folder.

answered Aug 02 '20 at 06:17

Sreya Chakraborty

1

score -2 · Answer 14 · answered Oct 14 '20 at 12:58

-2

the file path you ran is wrong. So if you are working on windows, go to the correct file location with cd and rerun from there.

answered Oct 14 '20 at 12:58

huseyin

1

1

Post a code along with the reason for better understanding. – Jatin Mehrotra Oct 14 '20 at 13:21

npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\Nuwanst\package.json'

14 Answers14

Linked