ERR! addLocal Could not install /private/var/folders/cl/rk8c_n65471274j6vh56b7b80000gn/T/npm.65636/package

[gerrymiller]

I have been using Homebrew-installed node.js on my El Capitan Macbook Pro. I recently modified my configuration to let Homebrew manage Node.js only, but let me manage npm separately as described here: https://gist.github.com/DanHerbert/9520689. Since then, I am getting the following error message consistently - it doesn't seem to impact npm's ability to function, but philosophically the error bugs me. Any ideas on how best to diagnose/fix?

| ~ @ Gerry's MacBook (gerry) 
| => npm update -g
npm ERR! addLocal Could not install /private/var/folders/cl/rk8c_n65471274j6vh56b7b80000gn/T/npm.65636/package

[VeitSanner]

I encounter the same issue.

And as far as I have seen it applies as well to

npm outdated -g

[larssn]

Same problem, same procedure.
Stuck with npm v3.7.5 atm.

[pierredewilde]

Hi,

Same issue with sudo npm update -g.

This error is generated when trying to update npm itself:

sudo npm update -g npm

All other global packages are correctly updated.

Thanks,
Pierre

[ChasonTang]

Same issue in the npm v3.8.5, it have been disappear in v3.8.2,however, npm v3.8.2 couldn't upgrade to latest version by the command

npm update -g

so i reinstall the npm to the v3.8.5.there is disappointing that the issue is appear again.

[bronzeiii]

run this command, it resolved the issue for me

npm install -g npm@latest

[VeitSanner]

@bronzeiii, this has resolved the issue for me. Thanks for the update.

[JohnyDays]

Same problem with npm@3.10.7, I'm trying to install a private package from bitbucket.
Full log here:

npm ERR! addLocal Could not install /tmp/npm-3770-2e274f11/git-cache-5c5414c3/7777697552c5d76dd7d5647d677d342249ebb155
npm ERR! Linux 4.5.4-1-ARCH
npm ERR! argv "/home/johnydays/.nvm/versions/node/v6.5.0/bin/node" "/home/johnydays/.nvm/versions/node/v6.5.0/bin/npm" "i" "--save" "https://bitbucket.org/xxxxxx/xxxxxx"
npm ERR! node v6.5.0
npm ERR! npm  v3.10.7
npm ERR! code EISDIR
npm ERR! errno -21
npm ERR! syscall read

npm ERR! eisdir EISDIR: illegal operation on a directory, read
npm ERR! eisdir This is most likely not a problem with npm itself
npm ERR! eisdir and is related to npm not being able to find a package.json in
npm ERR! eisdir a package you are trying to install.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/johnydays/projects/master-admin/npm-debug.log

Also tried adding .git and using ssh url, both failed.
Going to manually link for now, hit me up if I can provide any more information that could help.

[larssn]

This should have been fixed at this point, so running npm install -g npm should now be enough.

[ericandrewlewis]

Make sure the github repository you're installing as a package has a package.json, that was my problem

[rishabh7257]

This could also be a problem if you are copying the files manually along with package.json which i did. Although you can see the file in the folder then too the npm install will fail. I resolved this issue by

1. deleting the package.json file in the project directory.
2. From CMD - 'npm init' (in the project directory).
3. Then 'npm install'

[BenGWeeks]

I was receiving a similar issue when running;

npm install ts-node --save-dev

Turns out I had to retype "--save-dev" as Word had used a different character for the dash that I had copied the command from.

[karnikamit]

@webtechy thanks! it worked like a charm when typed.

[npm-robot]

We're closing this issue as it has gone thirty days without activity. In our experience if an issue has gone thirty days without any activity then it's unlikely to be addressed. In the case of bug reports, often the underlying issue will be addressed but finding related issues is quite difficult and often incomplete.

If this was a bug report and it is still relevant then we encourage you to open it again as a new issue. If this was a feature request then you should feel free to open it again, or even better open a PR.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

[rishabhkashyap]

running below command worked for me
npm install -g npm@latest