无论我在什么目录下,无论我在cmd.exe中键入“npm”后,我都被这个错误卡住了。下面是npm-debug.log:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js' ]
2 info using npm@2.14.12
3 info using node@v4.2.6
4 verbose stack Error: EISDIR: illegal operation on a directory, read
4 verbose stack     at Error (native)
5 verbose cwd C:\Users\me
6 error Windows_NT 6.1.7601
7 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
8 error node v4.2.6
9 error npm  v2.14.12
10 error code EISDIR
11 error errno -4068
12 error syscall read
13 error eisdir EISDIR: illegal operation on a directory, read
13 error eisdir This is most likely not a problem with npm itself
13 error eisdir and is related to npm not being able to find a package.json in
13 error eisdir a package you are trying to install.
14 verbose exit [ -4068, true ]

I have tried and uninstalling/reinstalling nodejs multiple times, I even deleted npm and npm-cache folders in C:\Users\me\AppData\Roaming. I'm not sure what went wrong to cause this. One second it was working fine, and now I can't get rid of this error. The explanation in the log does not make sense, as it gives this error in any directory. I should note that running a command prompt as administrator does not give this error. I'm pulling my hair out this Friday evening trying to get this fixed, any help would be greatly appreciated!


当前回答

只需删除c:users>'username'中的.npmrc文件夹,并尝试运行命令,它将被解决!

其他回答

我使用的是Laravel v8.56.0的Mix v6.0.29

在webpack.mix.js中,当复制目录时使用

mix.copyDirectory(“resources/js”, “public/js”);

检查内部文件夹,它不应该包含点/s(.),否则,这个错误将弹出。

我认为对于这个特定的版本,路径(或文件夹)与点/s后面跟着一些字符,将类似于文件扩展名,然后将被视为“文件”,不管它是否是“文件夹”。

这些奇怪的错误最近发生在我的OSX机器上。

我可以用快速而肮脏的方式来帮助自己:

sudo chmod -R 777 /usr/local/lib/node_modules/

似乎有什么东西打乱了所有全局节点模块的访问权限。

做一个完整的卸载,包括删除路径等,重新安装已经解决了这个问题,虽然非常奇怪的问题。

如何从Windows中完全删除node.js

对我来说,这是因为我走错了路;它应该是一个文件的路径,但我错误地使用了一个目录的路径:

改变:

path.resolve(__dirname, '../');

到这个:

path.resolve(__dirname, '../.env')

我在更改一些npm设置时遇到了同样的问题。我在一个npm config set命令中犯了一个错误,这添加了一行指向C:\Users\{User}\.npmrc中不存在的目录。当我手动从.npmrc中删除这一行后,问题就消失了。