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 gt 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

User · Answer

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

User · Answer

Run command - npm init No file directory found issue got resolved

User · Answer

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

User · Answer

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  lt pkgname gt   e g express  and a new node modules folder will be created for your

User · Answer

Have you created a package json file  Maybe run this command first again    C  Users Nuwanst Documents NodeJS 3 chat gt npm init   It creates a package json file in your folder   Then run    C  Users Nuwanst Documents NodeJS 3 chat gt 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

User · Answer

update version in package json is working for me

User · Answer

You can use npm init to create a package json

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

This worked for me  I simply cd  quot C  the path of the project where package json is quot  before I ran  quot npm start quot

User · Answer

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

User · Answer

Delete  package-lock json it works for me  then npm install

User · Answer

we need to create package json by entering npm init and enter package name as package json and optionally fill other requirements else press enter and at last enter yes to confirm  Great   Now install any npm package without any error   npm install  lt package name gt    Windows10

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

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

Examples related to javascript

Examples related to node.js

Examples related to npm

Examples related to server

Examples related to node-modules