blocks|key|183220|text|我认为您编译的咖啡脚本在发布的npm包中丢失了。尝试编写一个prepublish命令。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|183221|entityMap|0|LINK|mutability|MUTABLE|url|https://npmjs.org/doc/scripts.html^0|U|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I think your compiled coffee script is missing from the published npm package. Try writing a <a href="https://npmjs.org/doc/scripts.html" rel="nofollow">prepublish</a> command.

blocks|key|181633|text|好的，看起来NPM使用你的.gitignore作为.npmignore文件的基础，因此忽略了/lib。如果您将一个空白的.npmignore文件添加到应用程序的根目录中，那么一切都应该正常工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|181634|一种更好、更明确的方法是使用允许列表而不是不允许列表，并使用package.json中的“文件”字段来指定包中的文件。|181635|编辑-有关此行为的更多信息，请单击此处：https://docs.npmjs.com/cli/v7/using-npm/developers#keeping-files-out-of-your-package|181636|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.npmjs.com/cli/v7/using-npm/developers#keeping-files-out-of-your-package^0|D|A|P|A|1A|4|1O|A|0|0|K|2C|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@]|D|@$9|12|A|13|1|14]]|E|$]]|$1|J|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

Ok it looks like NPM is using your <code>.gitignore</code> as a base for the <code>.npmignore</code> file, and thus ignores <code>/lib</code>. If you add a blank <code>.npmignore</code> file into the root of your application, everything should work.
A better, more explicit approach is to use an allow-list rather than a disallow-list, and use the &quot;files&quot; field in package.json to specify the files in your package.
[edit] - more info on this behaviour here: <a href="https://docs.npmjs.com/cli/v7/using-npm/developers#keeping-files-out-of-your-package" rel="nofollow noreferrer">https://docs.npmjs.com/cli/v7/using-npm/developers#keeping-files-out-of-your-package</a>

blocks|key|3005302|text|请试试这个|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3005303|SET+HTTP_PROXY=<proxy_name>|code-block|syntax|javascript|3005304|然后试着让command.It正常工作|3005305|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Please try this

<pre><code>SET HTTP_PROXY=&lt;proxy_name&gt;
</code></pre>

Then try that command.It will work

blocks|key|2792865|text|当我尝试运行npm+install+-g+bower时，这个问题不知何故在Mac上出现了。它给了我许多错误，因为我找不到像graceful-fs这样的东西。我不确定我最初是如何安装npm的，但它看起来可能是使用自制软件与node一起安装的。我第一次跑|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2792866|brew+uninstall+node|code-block|syntax|javascript|2792867|这将从我的路径中删除node和npm。从那里我只是重新安装了它|2792868|brew+install+node|2792869|当它完成时，我的路径上有了node和npm，我可以运行|2792870|rm+-rf+~/.npm
npm+install+-g+bower|2792871|这样就成功地安装了bower。|2792872|更新brew公式和升级安装程序似乎对我不起作用，我不确定原因。删除.npm文件夹对其他人来说是可行的，我尝试过，但没有成功。我这次这么做是为了以防万一。还请注意，以下两种方法都没有为我解决问题，尽管它为其他人解决了问题：|2792873|npm+cache+clean
sudo+npm+cache+clean|2792874|entityMap^0|6|K|0|0|A|4|F|3|0|0|D|4|I|3|0|0|0|X|4|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|19|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1F|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1G|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|W|3|X|5|H|7|1K|8|@]|D|@]|E|$I|J]]|$1|Y|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|Z|$]]

This problem somehow arose for me on Mac when I was trying to run <code>npm install -g bower</code>. It was giving me a number of errors for not being able to find things like graceful-fs. I'm not sure how I installed npm originally, but it looks like perhaps it came down with node using homebrew. I first ran

<pre><code>brew uninstall node
</code></pre>

This removed both <code>node</code> and <code>npm</code> from my path. From there I just reinstalled it

<pre><code>brew install node
</code></pre>

When it completed I had <code>node</code> and <code>npm</code> on my path and I was able to run

<pre><code>rm -rf ~/.npm
npm install -g bower
</code></pre>

This then installed bower successfully.

Updating the brew formulas and upgrading the installs didn't seem to work for me, I'm not sure why. The removal of the <code>.npm</code> folder was something that had worked for other people, and I had tried it without success. I did it this time just in case. Note also that neither of the following solved the problem for me, although it did for others:

<pre><code>npm cache clean
sudo npm cache clean
</code></pre>

blocks|key|183275|text|我也遇到了类似的问题，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|183276|npm+cache+clean|code-block|syntax|javascript|183277|解决了它。|183278|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I ran into a similar problem, 

<pre><code>npm cache clean
</code></pre>

solved it.

blocks|key|181668|text|我尝试了我在网上找到的所有东西(npm+cache+clear和rm+-rf+~/.npm)，但似乎都不起作用。解决这个问题的方法是将node+(和npm)更新到最新版本。试试看。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|181669|entityMap^0|G|F|W|D|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

I tried all the stuff I found on the net (<code>npm cache clear</code> and <code>rm -rf ~/.npm</code>), but nothing seems to work. What solved the issue was updating node (and npm) to the latest version. Try that.

blocks|key|180710|text|在我的例子中(多代码ENOENT+errno34)，问题出在~/.npm/目录访问上。在它里面有一些拥有root:root权限的子目录，当我以普通用户(没有sudo)的身份运行命令时，这些子目录会导致问题。因此，我将~/.npm/目录中所有子目录和文件的所有权更改为本地用户和组。这在我的Ubuntu上做到了(在Mac上也应该可以)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|180711|$+sudo+chown+yourusername.yourgroupname+~/.npm/+-R|code-block|syntax|javascript|180712|你应该知道你的用户名，对吧？如果不是，则运行$+whoami并将您的组名也替换为它，如下所示：|180713|$+sudo+chown+johnb.johnb+~/.npm/+-R|180714|编辑：|180715|测试用例|BOLD|180716|从我的本地帐户/home/johnb+I+npm-全局安装了一些yeoman生成器，如下所示：|180717|$+sudo+npm+install+-g+generator-laravel|180718|问题性质|180719|上述操作导致一些依赖项被安装在~/.npm/目录中，拥有root:root所有权(由于sudo+...)。显然，当提取依赖项并将其写入本地用户子目录~/.npm/时，npm不会以本地用户身份运行(或更改依赖项子目录的所有权)。只要npm对基本的unix文件系统安全问题如此粗心大意，问题就会再次发生。|180720|解决方案|180721|180722|会持续检查~/.npm/是否包含具有所有权(和/或权限)而不是您的本地用户帐户的子目录，特别是当您使用sodo+(根用户)安装或更新某些内容时。如果是，请将~/.npm/内部的所有权更改为本地用户recursively.|ordered-list-item|180723|Ask+npm,+bower,+grunt,+...社区，这样他们就可以像我上面描述的那样解决此问题。|180724|180725|entityMap^0|U|7|1G|9|26|4|30|7|0|0|M|8|0|0|0|0|4|0|7|B|W|6|0|0|0|4|0|F|7|S|9|17|8|22|7|0|0|4|0|0|5|7|1F|4|26|7|0|4|M|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1L|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|1P|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1R|8|@$9|1S|A|1T|B|S]]|D|@]|E|$]]|$1|T|3|U|5|6|7|1U|8|@$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]]|D|@]|E|$]]|$1|V|3|W|5|H|7|1Z|8|@]|D|@]|E|$I|J]]|$1|X|3|Y|5|6|7|20|8|@$9|21|A|22|B|S]]|D|@]|E|$]]|$1|Z|3|10|5|6|7|23|8|@$9|24|A|25|B|C]|$9|26|A|27|B|C]|$9|28|A|29|B|C]|$9|2A|A|2B|B|C]]|D|@]|E|$]]|$1|11|3|12|5|6|7|2C|8|@$9|2D|A|2E|B|S]]|D|@]|E|$]]|$1|13|3|-4|5|6|7|2F|8|@]|D|@]|E|$]]|$1|14|3|15|5|16|7|2G|8|@$9|2H|A|2I|B|C]|$9|2J|A|2K|B|C]|$9|2L|A|2M|B|C]]|D|@]|E|$]]|$1|17|3|18|5|16|7|2N|8|@$9|2O|A|2P|B|C]]|D|@]|E|$]]|$1|19|3|-4|5|6|7|2Q|8|@]|D|@]|E|$]]|$1|1A|3|-4|5|6|7|2R|8|@]|D|@]|E|$]]]|1B|$]]

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

<pre><code>$ sudo chown yourusername.yourgroupname ~/.npm/ -R
</code></pre>

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

<pre><code>$ sudo chown johnb.johnb ~/.npm/ -R
</code></pre>

EDIT:

Test case:

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

<pre><code>$ sudo npm install -g generator-laravel
</code></pre>

Problem nature:

Above action caused some dependencies being installed inside <code>~/.npm/</code> dir, having <code>root:root</code> ownership (because of <code>sudo ...</code>). 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 <code>~/.npm/</code>.
As long as npm would be so careless against fundamental unix filesystem security issues the problem would reoccur. 

Solution:

<ol>
<li>Continuosly check if <code>~/.npm/</code> contains subdirs with ownership (and/or permissions) other than your local user account, especially when you install or update something with <code>sodo</code> (root). If so, change the ownership inside <code>~/.npm/</code> to a local user recursively.</li>
<li>Ask <code>npm, bower, grunt, ...</code> community that they address this issue as I described it above.</li>
</ol>

blocks|key|3005431|text|在Windows中，我遇到了类似的错误。搜索粘贴应用程序数据并搜索字符串npm。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3005432|我在atlasboard\lib\package-dependency-manager.js和atlasboard\lib\cli\commands.js中都用'npm.cmd'替换了字符串'npm'+(包括引号)。这就解决了这个问题。|3005433|entityMap^0|10|3|0|2|18|1B|U|28|9|2N|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|I|$]]

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

I replaced the string <code>'npm'</code> (including quotes) with <code>'npm.cmd'</code> in both <code>atlasboard\lib\package-dependency-manager.js</code> and <code>atlasboard\lib\cli\commands.js</code>. That fixed the problem.

blocks|key|2792997|text|在全局安装(npm+install+-g+mymodule)包含不存在脚本的软件包时出现相同的错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2792998|在package.json中：|2792999|++++...
++++"bin":+{
++++++"module":+"./bin/module"
++++},
++++...|code-block|syntax|javascript|2793000|但是./bin/module并不存在，因为它被命名为modulejs。|2793001|entityMap^0|6|N|0|0|0|2|C|Q|8|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

The same error during global install (<code>npm install -g mymodule</code>) for package with a non-existing script.

In package.json:

<pre class="lang-json prettyprint-override"><code> ...
 "bin": {
 "module": "./bin/module"
 },
 ...
</code></pre>

But the <code>./bin/module</code> did not exist, as it was named <code>modulejs</code>.

blocks|key|180761|text|我遇到了一个类似的问题，原因不同：yo+node生成器将"files":+["lib/"]添加到我的package.json中，因为我的cli.js在lib/目录之外，所以在发布到npm时会跳过它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|180762|(+https://github.com/yeoman/generator-node/issues/63的约曼问题应该很快就会得到解决。)|180763|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/yeoman/generator-node/issues/63^0|H|7|S|H|1E|C|1W|6|23|4|0|2|1E|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|H|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

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

(Yeoman issue at <a href="https://github.com/yeoman/generator-node/issues/63" rel="nofollow">https://github.com/yeoman/generator-node/issues/63</a> it should be fixed soon.)

blocks|key|2793045|text|我在安装npm时遇到了这个错误，添加.npmignore并没有解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2793046|2793047|错误:+ENOENT，状态'C:\Users\My-UserName\AppData\Roaming\npm‘|blockquote|2793048|2793049|2793050|我试着打开上面提到的文件夹，但它并不存在。该错误已修复当我创建+npm文件夹中的漫游文件夹。|offset|length|style|BOLD|2793051|这是在Windows+8.1上|2793052|entityMap^0|0|0|0|0|0|T|2|W|3|14|2|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|T|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@$J|X|K|Y|L|M]|$J|Z|K|10|L|M]|$J|11|K|12|L|M]]|9|@]|A|$]]|$1|N|3|O|5|6|7|13|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|Q|$]]

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

<blockquote>
 Error: ENOENT, stat 'C:\Users\My-UserName\AppData\Roaming\npm'
</blockquote>

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

blocks|key|2793064|text|我收到错误消息"+error+:+ENOENT，stat+'C:\Users\userName\AppData\Roaming\+npm‘。但是没有这样的目录。创建了目录，npm安装开始工作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2793065|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was getting the error "Error: ENOENT, stat 'C:\Users\userName\AppData\Roaming\npm'. But there was no such directory. Created the directory and the npm install started working

blocks|key|183351|text|在尝试npm+install一堆依赖项时，我得到了类似的错误信息。事实证明，他们中的一些人无法在Debian/Ubuntu上安装，因为他们希望/usr/bin/node是节点可执行文件。要解决这个问题，你需要做|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|183352|sudo+ln+-s+nodejs+/usr/bin/node+|code-block|syntax|javascript|183353|或者更好的是，|183354|sudo+apt-get+install+nodejs-legacy|183355|有关更多信息，请访问：https://stackoverflow.com/a/21171188/7581|183356|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/21171188/7581^0|3|B|1Z|D|0|0|0|0|B|15|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|Q|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

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

<pre><code>sudo ln -s nodejs /usr/bin/node 
</code></pre>

or better yet, 

<pre><code>sudo apt-get install nodejs-legacy
</code></pre>

For more info: <a href="https://stackoverflow.com/a/21171188/7581">https://stackoverflow.com/a/21171188/7581</a>

blocks|key|179330|text|我在尝试安装grunt插件时遇到了这个错误。我发现我有一个过时的npm版本，在将npm更新到最新版本后，错误消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|179331|npm+install+-g+npm|code-block|syntax|javascript|179332|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

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

<pre><code>npm install -g npm
</code></pre>

blocks|key|179343|text|我也有同样的问题，只是发现了一个这里没有提到的处理方法。尽管我会为社区做贡献：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|179344|npm+install+-g+myapp没有复制bin目录。我发现这是因为我没有把它包含在我的package.json的files中|offset|length|style|CODE|179345|"files":+[
++"lib",
++"bin"+//+this+was+missing
]|code-block|syntax|javascript|179346|entityMap^0|0|0|K|O|3|1B|C|1O|5|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]|$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|N|$]]

I had the same problem, and just found a handling not mentioned here. Though I'd contribute to the community:

<code>npm install -g myapp</code> was not copying the <code>bin</code> directory. I found this to be because I did not include it in the <code>files</code> in my <code>package.json</code>

<pre><code>"files": [
 "lib",
 "bin" // this was missing
]
</code></pre>

blocks|key|3005618|text|我最近在Windows7+x64机器上升级到了Node4.2.1。运行时|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3005619|npm+install+-g+bower|code-block|syntax|javascript|3005620|我得到了一个类似的错误：|3005621|3005622|+npm错误！enoent环境:没有这样的文件或目录，请打开'C:\Users\THE_USERNAME\AppData\Local\Temp\npm-THE_HASH‘|blockquote|3005623|3005624|3005625|我认为这与AppData路径有关，所以我玩了一下|3005626|npm+config+edit|3005627|和|3005628|npm+config+edit+--global|3005629|要更改前缀、缓存和临时字段，但在新路径中收到相同的错误：|3005630|3005631|+npm错误！enoent+ENOENT:没有这样的文件或目录，请打开'C:\Users\THE_USERNAME\npm-temp\npm-THE_HASH‘|3005632|3005633|3005634|所有命令都是以管理员身份运行的，因此我拥有完全权限。|3005635|然后我认为现有文件有一些问题，所以我运行：|3005636|npm+cache+clean|3005637|但得到了相同的错误。但是，仍然有一些临时文件。使用cygwin手动删除所有临时数据最终为我解决了这个问题：|3005638|rm+-rf+bower+bower.cmd+node_modules+etc|3005639|如果你只有Windows+cmd，你可以使用类似这样的命令|3005640|rmdir+/S+THE_TEMP_DIR|3005641|删除所有子目录(尽管如果您有深度嵌套的节点依赖项，这是出了名的问题)|3005642|因此，也许在升级npm和使用bower或其他包的版本时会出现一些问题。对我来说，这似乎就是问题所在。|3005643|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1O|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1P|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1R|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1U|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1V|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1W|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|1X|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|Z|3|10|5|L|7|20|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|22|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|23|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|24|8|@]|9|@]|A|$]]|$1|17|3|18|5|D|7|25|8|@]|9|@]|A|$E|F]]|$1|19|3|1A|5|6|7|26|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|D|7|27|8|@]|9|@]|A|$E|F]]|$1|1D|3|1E|5|6|7|28|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|D|7|29|8|@]|9|@]|A|$E|F]]|$1|1H|3|1I|5|6|7|2A|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|6|7|2B|8|@]|9|@]|A|$]]|$1|1L|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]]|1M|$]]

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

<pre><code>npm install -g bower
</code></pre>

I got a similar error:

<blockquote>
 npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\THE_USERNAME\AppData\Local\Temp\npm-THE_HASH'
</blockquote>

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

<pre><code>npm config edit
</code></pre>

and

<pre><code>npm config edit --global
</code></pre>

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

<blockquote>
 npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\THE_USERNAME\npm-temp\npm-THE_HASH'
</blockquote>

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

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

<pre><code>npm cache clean
</code></pre>

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:

<pre><code>rm -rf bower bower.cmd node_modules etc
</code></pre>

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

<pre><code>rmdir /S THE_TEMP_DIR
</code></pre>

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

blocks|key|183455|text|我在本地安装的npm+install上遇到了类似的错误：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|183456|npm+ERR!+enoent+ENOENT:+no+such+file+or+directory,+stat+'[path/to/local/installation]/node_modules/grunt-contrib-jst'|code-block|syntax|javascript|183457|我不确定是什么导致了这个错误，但我最近在本地安装了几个新的节点模块，用自制软件升级了节点，并运行了'npm+update+-g‘。|183458|我解决此问题的唯一方法是完全删除本地node_modules目录，然后再次运行：|BOLD|183459|cd+[path/to/local/installation]
npm+rm+-rdf+node_modules
npm+install|183460|entityMap^0|7|B|0|0|0|0|14|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|W|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|X|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|Y|8|@$9|Z|A|10|B|O]]|D|@]|E|$]]|$1|P|3|Q|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|R|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|S|$]]

I was getting a similar error on <code>npm install</code> on a local installation:

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

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 <code>npm install</code> again:

<pre><code>cd [path/to/local/installation]
npm rm -rdf node_modules
npm install
</code></pre>

blocks|key|183471|text|在安装ionic时，我遇到以下错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|183472|环境:没有这样的文件或目录，请将'C:\Users\UserName\AppData\Roaming\npm\node_modules.staging\ansi-b11f0c4b‘'C:\Users\UserName\AppData\Roaming\npm\node_modules\ionic\node_modules\cordova-lib\node_modules\ansi’重命名为|183473|+115648错误|blockquote|183474|183475|183476|在该路径下没有名为ansi的文件夹。我在那里创建了它并正确安装了它。|offset|length|style|CODE|183477|entityMap^0|0|0|0|0|0|9|4|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@$K|W|L|X|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

While installing ionic I got below error

<blockquote>
 115648 error enoent ENOENT: no such file or directory, rename
 'C:\Users\UserName\AppData\Roaming\npm\node_modules.staging\ansi-b11f0c4b'
 -> 'C:\Users\UserName\AppData\Roaming\npm\node_modules\ionic\node_modules\cordova-lib\node_modules\ansi'
</blockquote>

There was no folder called <code>ansi</code> at that path. I created it there and it installed correctly.

blocks|key|183479|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|183480|安装最新版本的节点缓存运行:+npm+|ordered-list-item|183481|183482|运行:+npm+install+cordova+-g|183483|183484|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|J|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|K|7|@]|8|@]|9|$]]|$1|D|3|-4|4|C|6|L|7|@]|8|@]|9|$]]|$1|E|3|F|4|C|6|M|7|@]|8|@]|9|$]]|$1|G|3|-4|4|5|6|N|7|@]|8|@]|9|$]]|$1|H|3|-4|4|5|6|O|7|@]|8|@]|9|$]]]|I|$]]

<ol>
<li>Install latest version of node</li>
<li>Run: npm cache clean</li>
<li>Run: npm install cordova -g</li>
</ol>

blocks|key|3005834|text|我有一个类似的问题:错误！enoent+ENOENT:没有这样的文件或目录，chmod+'node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/sshpk/bin/sshpk-conv我尝试了以上所有的解决方案，但没有成功。我使用的是流浪箱，项目在一个共享文件夹中。当我将项目移到另一个未共享的文件夹(主机)时，问题似乎就在那里，瞧！问题解决了。以防其他人也在使用流浪汉。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3005835|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|180917|text|如果您尝试在项目目录中"make+install“，但出现以下错误，您可以尝试一下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|180918|rm+-rf+./node_modules
npm+cache+clear
npm+remove+sails|code-block|syntax|javascript|180919|然后你可以尝试"make+install“|180920|如果你有"npm+ERR！enoent+ENOENT:没有这样的文件或目录，chmod美化，然后你可以尝试安装一些以前版本的js-+'.../djam-backend/node_modules/js-beautify/js/bin/css-beautify.js'“，更多评论：https://github.com/beautify-web/js-beautify/issues/1247|offset|length|180921|"dependencies":+{
++...
++"js-beautify":+"1.6.14"
++...
}|180922|然后运行"make+install“。如果您没有其他需要更高版本(1.7.0)的依赖项，那么在这种情况下，您必须在packages.json中也降级此包。|180923|或|180924|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/beautify-web/js-beautify/issues/1247^0|0|0|0|3V|1J|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|13|8|@]|9|@$K|14|L|15|1|16]]|A|$]]|$1|M|3|N|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

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

<pre><code>rm -rf ./node_modules
npm cache clear
npm remove sails
</code></pre>

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: <a href="https://github.com/beautify-web/js-beautify/issues/1247" rel="nofollow noreferrer">https://github.com/beautify-web/js-beautify/issues/1247</a>

<pre><code>"dependencies": {
 ...
 "js-beautify": "1.6.14"
 ...
}
</code></pre>

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

blocks|key|180929|text|以上这些对我来说都不起作用。但是yarn+install成功了，然后npm+i开始工作了。不确定什么纱线固定，但快速简单的解决方案！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|180930|entityMap^0|G|C|Y|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

None of the above worked for me. But <code>yarn install</code> worked, then <code>npm i</code> started working. Not sure what yarn fixed, but quick and easy solution!

blocks|key|179492|text|如果你的node.js也以某种方式损坏了，你可能会得到这个错误。我通过完全卸载/重新启动/安装node.js修复了这个错误，它修复了这个错误，以及抛出的其他三个神秘错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|179493|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can get this error if your node.js is corrupted somehow as well. I fixed this error by uninstall/restart/install node.js completely and it fixed this error, along with the three other mysterious errors that are thrown.

blocks|key|179522|text|在升级到npm+6.1.0后，我遇到了类似的行为。它似乎工作过一次，但是当我尝试在文件系统上安装一个由path指定的包时，我进入了一个错误状态：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|179523|npm+ERR!+code+ENOENT
npm+ERR!+errno+-2
npm+ERR!+syscall+rename|code-block|syntax|javascript|179524|以下内容没有解决这个问题|BOLD|179525|179526|rm+-rf+node_modules|unordered-list-item|179527|npm+cache+clean+(给了npm+ERR!+As+of+npm@5,+the+npm+cache+self-heals....use+'npm+cache+verify'+instead.)|179528|npm+cache+verify|179529|rm+-rf+~/.npm|179530|179531|我是如何修复问题的|179532|179533|rm+package-lock.json|179534|179535|entityMap^0|8|5|0|0|4|8|0|0|0|J|0|0|F|J|1A|1X|V|0|0|G|0|0|D|0|0|0|0|0|K|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|19|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1A|8|@$9|1B|A|1C|B|M]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]|$1|O|3|P|5|Q|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|R|3|S|5|Q|7|1H|8|@$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|T|3|U|5|Q|7|1O|8|@$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|V|3|W|5|Q|7|1R|8|@$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|X|3|-4|5|6|7|1U|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1V|8|@]|D|@]|E|$]]|$1|10|3|-4|5|6|7|1W|8|@]|D|@]|E|$]]|$1|11|3|12|5|Q|7|1X|8|@$9|1Y|A|1Z|B|C]]|D|@]|E|$]]|$1|13|3|-4|5|6|7|20|8|@]|D|@]|E|$]]|$1|14|3|-4|5|6|7|21|8|@]|D|@]|E|$]]]|15|$]]

I encountered similar behavior after upgrading to npm <code>6.1.0</code>. 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:

<pre><code>npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
</code></pre>

The following things did not fix the problem:

<ul>
<li><code>rm -rf node_modules</code></li>
<li><code>npm cache clean</code> (gave <code>npm ERR! As of npm@5, the npm cache self-heals</code>....<code>use 'npm cache verify' instead.</code>)</li>
<li><code>npm cache verify</code></li>
<li><code>rm -rf ~/.npm</code></li>
</ul>

How I fixed the problem:

<ul>
<li><code>rm package-lock.json</code></li>
</ul>

blocks|key|179552|text|注意package.json中键“目录”和“文件”的无效值|type|unstyled|depth|inlineStyleRanges|entityRanges|data|179553|如果您使用新应用程序启动，并且希望完全空白启动，则必须在完全空的文件夹中启动，或者在其中包含有效的package.json文件。|179554|如果您不想首先创建package.json文件，只需输入：npm+i+some_package|offset|length|style|CODE|179555|应该在新子文件夹"node_modules“中正确安装名为"some_package”的包。|179556|如果您首先创建一个package.json文件，输入：npm+init保留所有默认值(只需单击ENTER)，您应该会得到一个有效的文件。|179557|它应该看起来像这样：|179558|{
++"name":+"yourfoldername",
++"version":+"1.0.0",
++"description":+"",
++"main":+"index.js",
++"scripts":+{
++++"test":+"echo+\"Error:+no+test+specified\"+&&+exit+1"
++},
++"author":+"",
++"license":+"ISC"
}|code-block|syntax|javascript|179559|请注意，缺少以下键：“目录”、“存储库”和“文件”。看起来，如果您为“目录”和/或“文件”使用了不正确的值，您将无法安装软件包。把这些钥匙放在外面，我的问题就解决了。|179560|另请注意键"main“。此参数存在，但它确实包含无效值。不存在文件"index.js“(尚不存在)。您可以安全地删除它。|179561|现在键入：npm+i+some_package并将名为"some_package“的包正确安装到一个新的子文件夹"node_modules”中。|179562|entityMap^0|0|0|T|I|0|0|R|8|0|0|0|0|0|5|I|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@$F|15|G|16|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@$F|19|G|1A|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1B|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|1C|8|@]|9|@]|A|$S|T]]|$1|U|3|V|5|6|7|1D|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1F|8|@$F|1G|G|1H|H|I]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|11|$]]

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: <code>npm i some_package</code>

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: <code>npm init</code>
Keep all the defaults (by just clicking ENTER), you should end up with a valid file.

It should look like this:

<pre><code>{
 "name": "yourfoldername",
 "version": "1.0.0",
 "description": "",
 "main": "index.js",
 "scripts": {
 "test": "echo \"Error: no test specified\" &amp;&amp; exit 1"
 },
 "author": "",
 "license": "ISC"
}
</code></pre>

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: <code>npm i some_package</code>
and package with name "some_package" should be installed correctly in a new sub folder "node_modules".

blocks|key|183637|text|Creating+a+new+React+app+in+C:\Users\CM\Downloads\react\github-profile.
Installing+packages.+This+might+take+a+couple+of+minutes.
Installing+react,+react-dom,+and+react-scripts...

npm+ERR!+path+C:\Users\CM\AppData\Roaming\npm-cache_cacache\content-+

v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996b1fa335b1
0893d67f7339e4af62bb688c0da2aaca839d4c9d51e2eb015eec65545008a3cad93d00f806

npm+ERR!+code+EPERM
npm+ERR!+errno+-4048
npm+ERR!+syscall+lstat
npm+ERR!+Error:+EPERM:+operation+not+permitted,+lstat+
'C:\Users\CM\AppData\Roaming\npm-cache_cacache\content-+
v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996
b1fa335b10893d67f7339e4af62bb688c0da2aaca839d4c9d51e2eb015eec6
5545008a3cad93d00f806'
npm+ERR!+{+[Error:+EPERM:+operation+not+permitted,+lstat+
'C:\Users\CM\AppData\Roaming\npm-cache_cacache\content-+
v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996b1f+
a335b10893d67f7339e4af62bb688c0da2aaca839d4c9d51e2eb015eec6554500
8a3cad93d00f806']

npm+ERR!+cause:
npm+ERR!+{+Error:+EPERM:+operation+not+permitted,+lstat+
'C:\Users\CM\AppData\Roaming\npm-cache_cacache\content-+
v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996b1
fa335b10893d67f7339e4+
af62bb688c0da2aaca839d4c9d51e2eb015eec65545008a3cad93d00f806'
npm+ERR!+errno:+-4048,
npm+ERR!+code:+'EPERM',
npm+ERR!+syscall:+'lstat',
npm+ERR!+path:
npm+ERR!+'C:\Users\CM\AppData\Roaming\npm-cache\_cacache\content-+


npm+ERR!+stack:
npm+ERR!+'Error:+EPERM:+operation+not+permitted,+lstat+
'C:\Users\CM\AppData\Roaming\npm-cache\_cacache\content-+
v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996
b1fa335b10893d67f7339e4af62bb688c0da2aaca839d4c9d51e2eb015
eec65545008a3cad93d00f806'',
npm+ERR!+errno:+-4048,
npm+ERR!+code:+'EPERM',
npm+ERR!+syscall:+'lstat',
npm+ERR!+path:
npm+ERR!+'C:\Users\CM\AppData\Roaming\npm-cache\_cacache\content-+
v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996b1fa335
b10893d67f7339e4af62bb688c0da2aaca839d4c9d51e2eb015eec65545008a3cad93
d00f806',
npm+ERR!+parent:+'postcss-image-set-function'+}
npm+ERR!
npm+ERR!+The+operation+was+rejected+by+your+operating+system.
npm+ERR!+It's+possible+that+the+file+was+already+in+use+(by+a
text+editor+or+antivirus),
npm+ERR!+or+that+you+lack+permissions+to+access+it.
npm+ERR!
npm+ERR!+If+you+believe+this+might+be+a+permissions+issue,+please+double-+
check+thenpm+ERR!+permissions+of+the+file+and+its+containing+directories,+or+
try++running

npm+ERR!+the+command+again+as+root/Administrator+(though+this+is+not+
recommended).
npm+ERR!+A+complete+log+of+this+run+can+be+found+in:
npm+ERR!+C:\Users\CM\AppData\Roaming\npm-cache_logs\2019-03-22T10_
27_19_722Z-debug.log


Aborting+installation.
npm+install+--save+--save-exact+--loglevel+error+react+react-dom+react-+
scripts+++has+failed.

Deleting+generated+file...+node_modules
Deleting+generated+file...+package.json
Deleting+GitHub-profile/+from+C:\Users\CM\Downloads\reactDone.``|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|183638|我遇到了类似的错误，但我多次尝试运行create-react-app命令，最终创建了它，这就是我的互联网连接的问题。检查你的互联网连接|unstyled|183639|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>Creating a new React app in C:\Users\CM\Downloads\react\github-profile.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts...

npm ERR! path C:\Users\CM\AppData\Roaming\npm-cache_cacache\content- 

v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996b1fa335b1
0893d67f7339e4af62bb688c0da2aaca839d4c9d51e2eb015eec65545008a3cad93d00f806

npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall lstat
npm ERR! Error: EPERM: operation not permitted, lstat 
'C:\Users\CM\AppData\Roaming\npm-cache_cacache\content- 
v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996
b1fa335b10893d67f7339e4af62bb688c0da2aaca839d4c9d51e2eb015eec6
5545008a3cad93d00f806'
npm ERR! { [Error: EPERM: operation not permitted, lstat 
'C:\Users\CM\AppData\Roaming\npm-cache_cacache\content- 
v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996b1f 
a335b10893d67f7339e4af62bb688c0da2aaca839d4c9d51e2eb015eec6554500
8a3cad93d00f806']

npm ERR! cause:
npm ERR! { Error: EPERM: operation not permitted, lstat 
'C:\Users\CM\AppData\Roaming\npm-cache_cacache\content- 
v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996b1
fa335b10893d67f7339e4 
af62bb688c0da2aaca839d4c9d51e2eb015eec65545008a3cad93d00f806'
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'lstat',
npm ERR! path:
npm ERR! 'C:\Users\CM\AppData\Roaming\npm-cache\_cacache\content- 


npm ERR! stack:
npm ERR! 'Error: EPERM: operation not permitted, lstat 
'C:\Users\CM\AppData\Roaming\npm-cache\_cacache\content- 
v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996
b1fa335b10893d67f7339e4af62bb688c0da2aaca839d4c9d51e2eb015
eec65545008a3cad93d00f806'',
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'lstat',
npm ERR! path:
npm ERR! 'C:\Users\CM\AppData\Roaming\npm-cache\_cacache\content- 
v2\sha512\36\c6\c3e97514319bc1c6d40026e58325e782e1016c996b1fa335
b10893d67f7339e4af62bb688c0da2aaca839d4c9d51e2eb015eec65545008a3cad93
d00f806',
npm ERR! parent: 'postcss-image-set-function' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a
text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double- 
check thenpm ERR! permissions of the file and its containing directories, or 
try running

npm ERR! the command again as root/Administrator (though this is not 
recommended).
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\CM\AppData\Roaming\npm-cache_logs\2019-03-22T10_
27_19_722Z-debug.log


Aborting installation.
npm install --save --save-exact --loglevel error react react-dom react- 
scripts has failed.

Deleting generated file... node_modules
Deleting generated file... package.json
Deleting GitHub-profile/ from C:\Users\CM\Downloads\reactDone.``
</code></pre>

i was facing similar error but i tried to run create-react-app command many times and finally it was created , this was the problem with my internet connection.
check your internet connection

blocks|key|2793541|text|第一件事|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2793542|+npm+rm+-rdf+node_modules|code-block|syntax|javascript|2793543|那就这么做|2793544|npm+install|2793545|之后，安装您想要添加的任何文件|2793546|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

First do

<pre><code> npm rm -rdf node_modules
</code></pre>

then do

<pre><code>npm install
</code></pre>

After that install whatever files you want to add

blocks|key|2793568|text|在为webpack的码头容器中使用npm时，也出现了类似的错误。该问题是由docker+run的--user命令行参数引起的，因为其中的给定用户和组不知何故弄乱了本地卷上的权限。希望这对某些人有帮助:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2793569|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Had a similar error with npm in a docker container for webpack. The issue was caused by the --user command line argument of docker run, because the given user and group in there somehow messed up the rights on the local volume. Hope this helps someone :)

blocks|key|3006151|text|几乎什么都试过了，最后是这个：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3006152|只需删除node_modules，然后再次运行'npm+install'|offset|length|style|CODE|3006153|entityMap^0|0|N|D|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Tried nearly everything then finally this:

Simply remove node_modules then run <code>'npm install'</code> again

blocks|key|182035|text|我在ubuntu上也遇到了同样的问题，于是我关闭了终端并打开了一个新的，从而解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|182036|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|3006171|text|关闭Android+Studio为我解决了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3006172|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Closing Android Studio solved this error for me.

blocks|key|182044|text|删除package-lock.json文件，然后运行npm+install|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|182045|entityMap^0|Q|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Delete package-lock.json file then run <code>npm install</code>

blocks|key|181057|text|我遇到过类似的问题，清除缓存，删除node_modules和重装都不起作用，所以把节点版本升级到最新版本对我来说是可行的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181058|sudo+npm+install+n+-g|code-block|syntax|javascript|181059|然后|181060|sudo+n+stable|181061|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I have came across similar issue, clearing cache, deleting node_modules and reinstalling didn't work, so upgrading the node version to latest one worked for me.
<pre><code>sudo npm install n -g
</code></pre>
then
<pre><code>sudo n stable
</code></pre>

blocks|key|2793666|text|这是因为没有package.json，只有包-lock.json|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2793667|尝试:+npm+init+--是|2793668|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It's because there is no package.json and only package-lock.json
Try: npm init --yes

blocks|key|181075|text|可以在另一个应用程序中打开node_modules目录，如"neatbeans“，并且禁止创建/重命名文件|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181076|可笑的是，在windows10机器上，这是我唯一的问题。|181077|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

node_modules directory could be opened in another application like &quot;neatbeans&quot; and file creation/renaming is forbidden
ridiculously -- on windows 10 machine -- that was my only problem

blocks|key|2793711|text|我有一个简单的解决方案，只需清除npm+cache即可。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2793712|sudo+npm+cache+clear+--force|code-block|syntax|javascript|2793713|然后删除node_modules+&+package-lock.json|2793714|sudo+rm+-rf+node_modules|2793715|sudo+rm+-rf+package-lock.json|2793716|现在使用npm安装依赖模块并启动服务器。|2793717|npm+install+&&+npm+start|2793718|entityMap^0|G|9|0|0|4|C|J|H|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|17|8|@]|D|@]|E|$]]|$1|S|3|T|5|H|7|18|8|@]|D|@]|E|$I|J]]|$1|U|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|V|$]]

I got the simple solution, just clear the <code>npm cache</code>.
<pre class="lang-sh prettyprint-override"><code>sudo npm cache clear --force
</code></pre>
then remove the <code>node_modules</code> &amp; <code>package-lock.json</code>
<pre class="lang-sh prettyprint-override"><code>sudo rm -rf node_modules
</code></pre>
<pre class="lang-sh prettyprint-override"><code>sudo rm -rf package-lock.json
</code></pre>
Now install the dependencies module using npm and start the server
<pre class="lang-sh prettyprint-override"><code>npm install &amp;&amp; npm start
</code></pre>

blocks|key|181083|text|首先安装mongoose依赖项|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181084|181085|+npm安装mongoose+npm安装|blockquote|181086|181087|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|J|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|K|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|L|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|M|8|@]|9|@]|A|$]]]|H|$]]

First install mongoose dependencies
<blockquote>
npm install mongoose
</blockquote>
<blockquote>
npm install
</blockquote>

blocks|key|179672|text|简单地解决问题，因为对文件的修改被锁定，或者您通过特定的保护程序锁定了分区上的权限，而证明是在另一个文件或硬盘驱动器上的另一个位置创建项目|type|unstyled|depth|inlineStyleRanges|entityRanges|data|179673|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Solve the problem simply because the modification to the file is locked, or you have locked the permissions on the partition through a specific protection program, and evidence of that is to create the project in another file or another place on the hard drive

blocks|key|179675|text|删除node_modules，package-lock.json并运行npm+install|type|unstyled|depth|inlineStyleRanges|entityRanges|data|179676|rm+-rf+node_modules
rm+-rf+package-lock.json
npm+install|code-block|syntax|javascript|179677|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Remove node_modules, package-lock.json and run npm install
<pre><code>rm -rf node_modules
rm -rf package-lock.json
npm install
</code></pre>

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.

<pre><code>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! &lt;http://github.com/isaacs/npm/issues&gt;
npm ERR! or email it to:
npm ERR! &lt;npm-@googlegroups.com&gt;

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
</code></pre>

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.

<ul>
<li>Upgrade npm (<code>sudo npm install -g npm</code>)</li>
<li>Clear the global npm cache (<code>sudo npm cache clear</code>)</li>
<li>Clear the user npm cache (<code>npm cache clear</code>)</li>
</ul>

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 <code>lib/cli.js</code> 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(<code>--no-bin-links</code>), when I tried the install with it, it worked fine.

So what's the deal? Is this some <a href="https://github.com/isaacs/npm/issues/3311#issuecomment-16011860" rel="noreferrer">weird fringe case bug</a> that has no solution yet?

Edit: For reference, <a href="https://github.com/giodamelio/takeapeek" rel="noreferrer">here</a> is the module I uploaded

npm install errors with Error: ENOENT, chmod

Android Studio

文件系统

服务器

Android

Windows

容器

Docker

GitHub

Ubuntu

Debian

Linux

我正在尝试全局安装我刚刚发布的npm模块。每次我尝试安装时，无论是从npm还是从文件夹，我都会得到这个错误。npm ERR! Error: ENOENT, chmod '/usr/local/lib/node_modules/takeapeek/lib/cmd.js'npm ERR! If you need help,...

问npm安装错误，错误: ENOENT，chmod
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问npm安装错误，错误: ENOENT，chmodEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问npm安装错误，错误: ENOENT，chmod
EN