[英]This error happens for every npm installation: “npm ERR! Cannot read property 'resolve' of undefined.”
Intro 介绍
Greetings, all! 大家好!
I'm on a dual boot system where Node, NPM, and the like worked well in Windows 7, but since Win7 has stopped booting - perhaps due to hardware problems - that leaves Windows 10. 我使用的是双启动系统,其中Node,NPM等在Windows 7中运行良好,但是由于Win7已停止启动(可能由于硬件问题),因此退出了Windows 10。
Every time I try using npm install (or some variant, like npm i -g), I get an error at least similar to what is listed below. 每当我尝试使用npm install(或某些变体,例如npm i -g)时,都会收到至少与下面列出的错误类似的错误。 This has prevented me from using npm i to get the newest npm.
这使我无法使用npm i来获取最新的npm。
I have tried finding and deleting package.json, but I'm unsure which package.json to remove. 我尝试查找并删除package.json,但不确定要删除哪个 package.json。 There was one in C:\\users\\\\ but that has since been deleted.
C:\\ users \\\\中有一个,但是此后已删除。 Moving or deleting node_modules from my node or npm directory hasn't fixed the problem.
从我的节点或npm目录中移动或删除node_modules并不能解决问题。
I've tried checking the Internet for various solutions to this problem, including installing the latest NodeJS. 我尝试检查Internet以找到解决此问题的各种方法,包括安装最新的NodeJS。
Versions 版本号
Obtained via node -v and npm -v. 通过节点-v和npm -v获得。
Node: 10.16 节点:10.16
NPM: 6.9 NPM:6.9
This is the log which displays upon running npm i -g npm. 这是运行npm i -g npm时显示的日志。
0 info it worked if it ends with ok
1 verbose cli [ 'F:\\NodeJS\\node.exe',
1 verbose cli 'F:\\NodeJS\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'i',
1 verbose cli 'npm',
1 verbose cli '-g' ]
2 info using npm@6.9.0
3 info using node@v10.16.0
4 verbose npm-session c2c7a7280bf360c8
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 silly fetchPackageMetaData error for npm@latest Cannot read property 'resolve' of undefined
8 timing stage:rollbackFailedOptional Completed in 1ms
9 timing stage:runTopLevelLifecycles Completed in 32ms
10 verbose stack TypeError: Cannot read property 'resolve' of undefined
10 verbose stack at regFetch (F:\NodeJS\node_modules\npm\node_modules\npm-registry-fetch\index.js:76:23)
10 verbose stack at fetchPackument (F:\NodeJS\node_modules\npm\node_modules\pacote\lib\fetchers\registry\packument.js:42:10)
10 verbose stack at packument (F:\NodeJS\node_modules\npm\node_modules\pacote\lib\fetchers\registry\packument.js:20:10)
10 verbose stack at getManifest (F:\NodeJS\node_modules\npm\node_modules\pacote\lib\fetchers\registry\manifest.js:22:10)
10 verbose stack at manifest (F:\NodeJS\node_modules\npm\node_modules\pacote\lib\fetchers\registry\manifest.js:13:10)
10 verbose stack at Object.manifest (F:\NodeJS\node_modules\npm\node_modules\pacote\lib\fetchers\registry\index.js:17:12)
10 verbose stack at Object.Fetcher#manifest [as manifest] (F:\NodeJS\node_modules\npm\node_modules\genfun\lib\genfun.js:15:38)
10 verbose stack at manifest (F:\NodeJS\node_modules\npm\node_modules\pacote\lib\fetch.js:23:18)
10 verbose stack at pinflight (F:\NodeJS\node_modules\npm\node_modules\pacote\manifest.js:24:12)
10 verbose stack at F:\NodeJS\node_modules\npm\node_modules\promise-inflight\inflight.js:29:24
10 verbose stack at Promise._execute (F:\NodeJS\node_modules\npm\node_modules\bluebird\js\release\debuggability.js:313:9)
10 verbose stack at Promise._resolveFromExecutor (F:\NodeJS\node_modules\npm\node_modules\bluebird\js\release\promise.js:483:18)
10 verbose stack at new Promise (F:\NodeJS\node_modules\npm\node_modules\bluebird\js\release\promise.js:79:10)
10 verbose stack at _inflight (F:\NodeJS\node_modules\npm\node_modules\promise-inflight\inflight.js:28:25)
10 verbose stack at F:\NodeJS\node_modules\npm\node_modules\promise-inflight\inflight.js:22:14
10 verbose stack at tryCatcher (F:\NodeJS\node_modules\npm\node_modules\bluebird\js\release\util.js:16:23)
11 verbose cwd C:\Users\Gec
12 verbose Windows_NT 10.0.17134
13 verbose argv "F:\\NodeJS\\node.exe" "F:\\NodeJS\\node_modules\\npm\\bin\\npm-cli.js" "i" "npm" "-g"
14 verbose node v10.16.0
15 verbose npm v6.9.0
16 error Cannot read property 'resolve' of undefined
17 verbose exit [ 1, true ]
I had the same problem with nodejs
10.16.0 (Windows x64 version) and npm
6.9.0. 我对
nodejs
10.16.0(Windows x64版本)和npm
6.9.0遇到了相同的问题。 After uninstalling and downgrading to nodejs
10.15.3 and npm
6.4.1 npm i
seems to work correctly again. 在卸载并降级到
nodejs
10.15.3和npm
6.4.1 npm i
似乎可以再次正常工作。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.