Не удается установить пакет error saving catalog

I am trying to globally install an npm module I just published. Every time I try to install, either from npm or the folder, I get this error.

npm ERR! Error: ENOENT, chmod '/usr/local/lib/node_modules/takeapeek/lib/cmd.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 3.8.0-19-generic
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "takeapeek"
npm ERR! cwd /home/giodamlio
npm ERR! node -v v0.10.6
npm ERR! npm -v 1.3.6
npm ERR! path /usr/local/lib/node_modules/takeapeek/lib/cmd.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/giodamlio/npm-debug.log
npm ERR! not ok code 0

I am using sudo and I have triple checked everything in the package everything should work. I did some searching around, and saw a couple of similer cases none of which have been resolved. Here is what I tried.

• Upgrade npm (sudo npm install -g npm)
• Clear the global npm cache (sudo npm cache clear)
• Clear the user npm cache (npm cache clear)

I noticed that the error had to do with the file I am linking to the path, specifically when npm tried to do a chmod. That shouldn’t be a problem, my lib/cli.js has normal permissions, and npm has superuser permissions during this install.

After digging through the npm docs I found an option that would stop npm from making the bin links(--no-bin-links), when I tried the install with it, it worked fine.

So what’s the deal? Is this some weird fringe case bug that has no solution yet?

Edit: For reference, here is the module I uploaded

I encountered similar behavior after upgrading to npm 6.1.0. It seemed to work once, but then I got into a state with this error while trying to install a package that was specified by path on the filesystem:

npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename

The following things did not fix the problem:

• rm -rf node_modules
• npm cache clean (gave npm ERR! As of npm@5, the npm cache self-heals….use 'npm cache verify' instead.)
• npm cache verify
• rm -rf ~/.npm

How I fixed the problem:

• rm package-lock.json

answered Jul 12, 2018 at 12:50

I was getting this error on npm install and adding .npmignore did not solve it.

Error: ENOENT, stat ‘C:UsersMy-UserNameAppDataRoamingnpm’

I tried going to the mentioned folder and it did not exist.
The error was fixed when I created npm folder in Roaming folder.

This is on Windows 8.1

answered Nov 15, 2014 at 23:08

answered Apr 13, 2021 at 6:00

I was getting a similar error on npm install on a local installation:

npm ERR! enoent ENOENT: no such file or directory, stat '[path/to/local/installation]/node_modules/grunt-contrib-jst'

I am not sure what was causing the error, but I had recently installed a couple of new node modules locally, upgraded node with homebrew, and ran ‘npm update -g’.

The only way I was able to resolve the issue was to delete the local node_modules directory entirely and run npm install again:

cd [path/to/local/installation]
npm rm -rdf node_modules
npm install

answered Dec 31, 2015 at 0:40

I have a similar problem specifucally :
ERR! enoent ENOENT: no such file or directory, chmod ‘node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/sshpk/bin/sshpk-conv
I tried all above solutions but no luck.
I was using vagrant box, and the project was in a shared folder. The problems seems to be only there, when I move the project to another not shared folder (woth host), voila! problem solved.
Just in case another person was using also vagrant

I got the simple solution, just clear the npm cache.

sudo npm cache clear --force

then remove the node_modules & package-lock.json

sudo rm -rf node_modules

sudo rm -rf package-lock.json

Now install the dependencies module using npm and start the server

npm install && npm start

answered Jul 17, 2021 at 2:38

I got a similar error message when trying to npm install a bunch of dependencies. Turns out some of them fail to install on Debian/Ubuntu because they expect /usr/bin/node to be the node executable. To fix, you need do

sudo ln -s nodejs /usr/bin/node 

or better yet,

sudo apt-get install nodejs-legacy

For more info: https://stackoverflow.com/a/21171188/7581

I got this error while trying to install a grunt plugin. i found i had an outdated version of npm and the error went away after updating npm to the latest version

npm install -g npm

answered Apr 4, 2015 at 16:13

I think your compiled coffee script is missing from the published npm package. Try writing a prepublish command.

In my case (multiple code ENOENT errno 34) problem was with ~/.npm/ directory access. Inside it there were some subdirs having root:root rights, which were causing problems while I run commands as normal user (without sudo). So I changed ownership of all subdirs and files inside ~/.npm/ dir into my local user and group. That did the trick on my Ubuntu (on Mac should work too).

$ sudo chown yourusername.yourgroupname ~/.npm/ -R

You should know your user name, right? If no then run $ whoami and substitute your group name with it too, like this:

$ sudo chown johnb.johnb ~/.npm/ -R

EDIT:

Test case:

From my local account /home/johnb I npm-installed globally some generator for yeoman, like this:

$ sudo npm install -g generator-laravel

Problem nature:

Above action caused some dependencies being installed inside ~/.npm/ dir, having root:root ownership (because of sudo ...). Evidently npm does not run as local user (or change dependencies subdirs ownership afterwards) when pulling dependencies and writing them to a local user subdir ~/.npm/.
As long as npm would be so careless against fundamental unix filesystem security issues the problem would reoccur.

Solution:

1. Continuosly check if ~/.npm/ contains subdirs with ownership (and/or permissions) other than your local user account, especially when you install or update something with sodo (root). If so, change the ownership inside ~/.npm/ to a local user recursively.

2. Ask npm, bower, grunt, ... community that they address this issue as I described it above.

answered May 28, 2014 at 22:10

Had a similar Issue but I was in wrong directory please cross check the path of thee file & the run npm start

answered May 24, 2014 at 16:49

In Windows I had a similar error.
Search paste App Data and search for the string npm.

I replaced the string 'npm' (including quotes) with 'npm.cmd' in both atlasboardlibpackage-dependency-manager.js and atlasboardlibclicommands.js. That fixed the problem.

1. Install latest version of node
2. Run: npm cache clean
3. Run: npm install cordova -g

answered Jan 10, 2017 at 3:29

answered May 26, 2018 at 4:04

Be careful with invalid values for keys «directories» and «files» in package.json

If you start with a new application, and you want to start completely blank, you have to
either start in a complete empty folder or have a valid package.json file in it.

If you do not want to create a package.json file first, just type: npm i some_package

Package with name «some_package» should be installed correctly in a new sub folder «node_modules».

If you create a package.json file first, type: npm init
Keep all the defaults (by just clicking ENTER), you should end up with a valid file.

It should look like this:

{
  "name": "yourfoldername",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo "Error: no test specified" && exit 1"
  },
  "author": "",
  "license": "ISC"
}

Note that the following keys are missing: «directories«, «repository» and «files«. It looks like if you use incorrect values for «directories» and/or «files«, you are not able to install the package. Leaving these keys out, solved the issue for me.

Also note key «main«. This one is present, but it does contain an invalid value. No file «index.js» exists (yet). You can safely remove it.

Now type: npm i some_package
and package with name «some_package» should be installed correctly in a new sub folder «node_modules».

answered Oct 16, 2018 at 13:16

answered Mar 16, 2020 at 21:28

Tried nearly everything then finally this:

Simply remove node_modules then run 'npm install' again

answered May 3, 2020 at 15:08

I had the same problem on ubuntu, and got rid of the problem by closing the terminal and opening a new one.

It’s because there is no package.json and only package-lock.json

Try: npm init —yes

answered Jul 3, 2021 at 18:14

I had a similar issue with a different cause: the yo node generator had added "files": ["lib/"] to my package.json and because my cli.js was outside of the lib/ directory, it was getting skipped when publishing to npm.

(Yeoman issue at https://github.com/yeoman/generator-node/issues/63 it should be fixed soon.)

answered Nov 6, 2014 at 16:51

answered Jan 29, 2015 at 2:39

I recently upgraded to node 4.2.1 on a Windows 7 x64 machine. When running

npm install -g bower

I got a similar error:

npm ERR! enoent ENOENT: no such file or directory, open ‘C:UsersTHE_USERNAMEAppDataLocalTempnpm-THE_HASH’

Thinking it was related to the AppData path, I played around with

npm config edit

and

npm config edit --global

to change the prefix, cache and tmp fields but received the same error with the new paths:

npm ERR! enoent ENOENT: no such file or directory, open ‘C:UsersTHE_USERNAMEnpm-tempnpm-THE_HASH’

All commands were run as Administrator, so I had full permissions.

Then I thought there were some issues with existing files so I ran:

npm cache clean

But got the same error. However, there were still some temp files lying around. Manually removing all temp data with cygwin finally fixed the problem for me:

rm -rf bower bower.cmd node_modules etc

If you only have Windows cmd, you could use something like

rmdir /S THE_TEMP_DIR

to remove all subdirectories (although if you have deeply nested node dependencies, this is notoriously problematic)

So, maybe there is some issues with upgrading npm and having versions of bower or other packages hanging around. In my case that seemed to be the problem

answered Oct 30, 2015 at 16:45

If you tried to «make install» in your project directory with this error you can try it:

rm -rf ./node_modules
npm cache clear
npm remove sails

then you can try to «make install»

If you have the «npm ERR! enoent ENOENT: no such file or directory, chmod ‘…/djam-backend/node_modules/js-beautify/js/bin/css-beautify.js'» then you can try to install some previous version of the js-beautify, more comments: https://github.com/beautify-web/js-beautify/issues/1247

"dependencies": {
  ...
  "js-beautify": "1.6.14"
  ...
}

and the run «make install». It seem works in case if you have not other dependencies that requires higher version (1.7.0) in this case you must downgrade this packages also in the packages.json.

or

answered Sep 18, 2017 at 10:29

I am trying to globally install an npm module I just published. Every time I try to install, either from npm or the folder, I get this error.

npm ERR! Error: ENOENT, chmod '/usr/local/lib/node_modules/takeapeek/lib/cmd.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 3.8.0-19-generic
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "takeapeek"
npm ERR! cwd /home/giodamlio
npm ERR! node -v v0.10.6
npm ERR! npm -v 1.3.6
npm ERR! path /usr/local/lib/node_modules/takeapeek/lib/cmd.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/giodamlio/npm-debug.log
npm ERR! not ok code 0

I am using sudo and I have triple checked everything in the package everything should work. I did some searching around, and saw a couple of similer cases none of which have been resolved. Here is what I tried.

• Upgrade npm (sudo npm install -g npm)
• Clear the global npm cache (sudo npm cache clear)
• Clear the user npm cache (npm cache clear)

I noticed that the error had to do with the file I am linking to the path, specifically when npm tried to do a chmod. That shouldn’t be a problem, my lib/cli.js has normal permissions, and npm has superuser permissions during this install.

After digging through the npm docs I found an option that would stop npm from making the bin links(--no-bin-links), when I tried the install with it, it worked fine.

So what’s the deal? Is this some weird fringe case bug that has no solution yet?

Edit: For reference, here is the module I uploaded

I encountered similar behavior after upgrading to npm 6.1.0. It seemed to work once, but then I got into a state with this error while trying to install a package that was specified by path on the filesystem:

npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename

The following things did not fix the problem:

• rm -rf node_modules
• npm cache clean (gave npm ERR! As of npm@5, the npm cache self-heals….use 'npm cache verify' instead.)
• npm cache verify
• rm -rf ~/.npm

How I fixed the problem:

• rm package-lock.json

answered Jul 12, 2018 at 12:50

I was getting this error on npm install and adding .npmignore did not solve it.

Error: ENOENT, stat ‘C:UsersMy-UserNameAppDataRoamingnpm’

I tried going to the mentioned folder and it did not exist.
The error was fixed when I created npm folder in Roaming folder.

This is on Windows 8.1

answered Nov 15, 2014 at 23:08

answered Apr 13, 2021 at 6:00

I was getting a similar error on npm install on a local installation:

npm ERR! enoent ENOENT: no such file or directory, stat '[path/to/local/installation]/node_modules/grunt-contrib-jst'

I am not sure what was causing the error, but I had recently installed a couple of new node modules locally, upgraded node with homebrew, and ran ‘npm update -g’.

The only way I was able to resolve the issue was to delete the local node_modules directory entirely and run npm install again:

cd [path/to/local/installation]
npm rm -rdf node_modules
npm install

answered Dec 31, 2015 at 0:40

I have a similar problem specifucally :
ERR! enoent ENOENT: no such file or directory, chmod ‘node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/sshpk/bin/sshpk-conv
I tried all above solutions but no luck.
I was using vagrant box, and the project was in a shared folder. The problems seems to be only there, when I move the project to another not shared folder (woth host), voila! problem solved.
Just in case another person was using also vagrant

I got the simple solution, just clear the npm cache.

sudo npm cache clear --force

then remove the node_modules & package-lock.json

sudo rm -rf node_modules

sudo rm -rf package-lock.json

Now install the dependencies module using npm and start the server

npm install && npm start

answered Jul 17, 2021 at 2:38

I got a similar error message when trying to npm install a bunch of dependencies. Turns out some of them fail to install on Debian/Ubuntu because they expect /usr/bin/node to be the node executable. To fix, you need do

sudo ln -s nodejs /usr/bin/node 

or better yet,

sudo apt-get install nodejs-legacy

For more info: https://stackoverflow.com/a/21171188/7581

I got this error while trying to install a grunt plugin. i found i had an outdated version of npm and the error went away after updating npm to the latest version

npm install -g npm

answered Apr 4, 2015 at 16:13

I think your compiled coffee script is missing from the published npm package. Try writing a prepublish command.

In my case (multiple code ENOENT errno 34) problem was with ~/.npm/ directory access. Inside it there were some subdirs having root:root rights, which were causing problems while I run commands as normal user (without sudo). So I changed ownership of all subdirs and files inside ~/.npm/ dir into my local user and group. That did the trick on my Ubuntu (on Mac should work too).

$ sudo chown yourusername.yourgroupname ~/.npm/ -R

You should know your user name, right? If no then run $ whoami and substitute your group name with it too, like this:

$ sudo chown johnb.johnb ~/.npm/ -R

EDIT:

Test case:

From my local account /home/johnb I npm-installed globally some generator for yeoman, like this:

$ sudo npm install -g generator-laravel

Problem nature:

Above action caused some dependencies being installed inside ~/.npm/ dir, having root:root ownership (because of sudo ...). Evidently npm does not run as local user (or change dependencies subdirs ownership afterwards) when pulling dependencies and writing them to a local user subdir ~/.npm/.
As long as npm would be so careless against fundamental unix filesystem security issues the problem would reoccur.

Solution:

1. Continuosly check if ~/.npm/ contains subdirs with ownership (and/or permissions) other than your local user account, especially when you install or update something with sodo (root). If so, change the ownership inside ~/.npm/ to a local user recursively.

2. Ask npm, bower, grunt, ... community that they address this issue as I described it above.

answered May 28, 2014 at 22:10

Had a similar Issue but I was in wrong directory please cross check the path of thee file & the run npm start

answered May 24, 2014 at 16:49

In Windows I had a similar error.
Search paste App Data and search for the string npm.

I replaced the string 'npm' (including quotes) with 'npm.cmd' in both atlasboardlibpackage-dependency-manager.js and atlasboardlibclicommands.js. That fixed the problem.

1. Install latest version of node
2. Run: npm cache clean
3. Run: npm install cordova -g

answered Jan 10, 2017 at 3:29

answered May 26, 2018 at 4:04

Be careful with invalid values for keys «directories» and «files» in package.json

If you start with a new application, and you want to start completely blank, you have to
either start in a complete empty folder or have a valid package.json file in it.

If you do not want to create a package.json file first, just type: npm i some_package

Package with name «some_package» should be installed correctly in a new sub folder «node_modules».

If you create a package.json file first, type: npm init
Keep all the defaults (by just clicking ENTER), you should end up with a valid file.

It should look like this:

{
  "name": "yourfoldername",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo "Error: no test specified" && exit 1"
  },
  "author": "",
  "license": "ISC"
}

Note that the following keys are missing: «directories«, «repository» and «files«. It looks like if you use incorrect values for «directories» and/or «files«, you are not able to install the package. Leaving these keys out, solved the issue for me.

Also note key «main«. This one is present, but it does contain an invalid value. No file «index.js» exists (yet). You can safely remove it.

Now type: npm i some_package
and package with name «some_package» should be installed correctly in a new sub folder «node_modules».

answered Oct 16, 2018 at 13:16

answered Mar 16, 2020 at 21:28

Tried nearly everything then finally this:

Simply remove node_modules then run 'npm install' again

answered May 3, 2020 at 15:08

I had the same problem on ubuntu, and got rid of the problem by closing the terminal and opening a new one.

It’s because there is no package.json and only package-lock.json

Try: npm init —yes

answered Jul 3, 2021 at 18:14

I had a similar issue with a different cause: the yo node generator had added "files": ["lib/"] to my package.json and because my cli.js was outside of the lib/ directory, it was getting skipped when publishing to npm.

(Yeoman issue at https://github.com/yeoman/generator-node/issues/63 it should be fixed soon.)

answered Nov 6, 2014 at 16:51

answered Jan 29, 2015 at 2:39

I recently upgraded to node 4.2.1 on a Windows 7 x64 machine. When running

npm install -g bower

I got a similar error:

npm ERR! enoent ENOENT: no such file or directory, open ‘C:UsersTHE_USERNAMEAppDataLocalTempnpm-THE_HASH’

Thinking it was related to the AppData path, I played around with

npm config edit

and

npm config edit --global

to change the prefix, cache and tmp fields but received the same error with the new paths:

npm ERR! enoent ENOENT: no such file or directory, open ‘C:UsersTHE_USERNAMEnpm-tempnpm-THE_HASH’

All commands were run as Administrator, so I had full permissions.

Then I thought there were some issues with existing files so I ran:

npm cache clean

But got the same error. However, there were still some temp files lying around. Manually removing all temp data with cygwin finally fixed the problem for me:

rm -rf bower bower.cmd node_modules etc

If you only have Windows cmd, you could use something like

rmdir /S THE_TEMP_DIR

to remove all subdirectories (although if you have deeply nested node dependencies, this is notoriously problematic)

So, maybe there is some issues with upgrading npm and having versions of bower or other packages hanging around. In my case that seemed to be the problem

answered Oct 30, 2015 at 16:45

If you tried to «make install» in your project directory with this error you can try it:

rm -rf ./node_modules
npm cache clear
npm remove sails

then you can try to «make install»

If you have the «npm ERR! enoent ENOENT: no such file or directory, chmod ‘…/djam-backend/node_modules/js-beautify/js/bin/css-beautify.js'» then you can try to install some previous version of the js-beautify, more comments: https://github.com/beautify-web/js-beautify/issues/1247

"dependencies": {
  ...
  "js-beautify": "1.6.14"
  ...
}

and the run «make install». It seem works in case if you have not other dependencies that requires higher version (1.7.0) in this case you must downgrade this packages also in the packages.json.

or

answered Sep 18, 2017 at 10:29