我在npm安装时遇到python2失败错误

link管理

链接快照平台

输入网页链接，自动生成快照
标签化管理网页链接

相关文章推荐

暴走的单车 · 在nodejs中将Json对象转换为数组 - · 2 周前 ·

奋斗的木瓜 · 如何将多维数组转换为json对象(node ...· 2 周前 ·

爱吹牛的刺猬 · 非常长的对象数组的NodeJS ...· 2 周前 ·

豪情万千的消防车 · nodejs读写json数据_json_发与 ...· 2 周前 ·

低调的菠菜 · Build fails behind ...· 昨天 ·

坐怀不乱的丝瓜 · 如何用python抓住房子 | ...· 1 月前 ·

骑白马的乒乓球 · linux删除jar包命令 - CSDN文库· 2 月前 ·

活泼的小马驹 · pb ...· 2 月前 ·

面冷心慈的八宝粥 · 千万粉丝博主“翻车”，被指“人设崩了”！最新回应· 2 月前 ·

痴情的上铺 · 汉语言文学一班-陕西师范大学档案馆· 4 月前 ·

在windows powershell中运行npm安装时出现错误,我需要使用node version 8.11.1,因此我使用nvm来执行此操作。我试着降级到Python2.7,但是没有成功,所以我升级回Python3.7仍然没有成功。这是我输出的错误,任何帮助都将不胜感激。这就是我要运行的项目 https://github.com/jadnco/static-boilerplate 我也尝试过每次删除节点模块,甚至从未生成package-lock.json,所以我没有删除它。

npm WARN deprecated [email protected]: ð  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated [email protected]: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
> [email protected] install C:\Users\andersk\sites\forkable-email-template\node_modules\node-sass
> node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-64_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-64_binding.node":
HTTP error 404 Not Found
Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g.
      export HTTP_PROXY=http://example.com:1234
or configure npm proxy via
      npm config set proxy http://example.com:8080
> [email protected] postinstall C:\Users\andersk\sites\forkable-email-template\node_modules\node-sass
> node scripts/build.js
Building: C:\Program Files\nodejs\node.exe C:\Users\andersk\sites\forkable-email-template\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ 'C:\\Program Files\\nodejs\\node.exe',
gyp verb cli   'C:\\Users\\andersk\\sites\\forkable-email-template\\node_modules\\node-gyp\\bin\\node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using [email protected]
gyp info using [email protected] | win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` failed Error: not found: python2
gyp verb `which` failed     at getNotFoundError (C:\Users\andersk\sites\forkable-email-template\node_modules\which\which.js:13:12)
gyp verb `which` failed     at F (C:\Users\andersk\sites\forkable-email-template\node_modules\which\which.js:68:19)
gyp verb `which` failed     at E (C:\Users\andersk\sites\forkable-email-template\node_modules\which\which.js:80:29)
gyp verb `which` failed     at C:\Users\andersk\sites\forkable-email-template\node_modules\which\which.js:89:16
gyp verb `which` failed     at C:\Users\andersk\sites\forkable-email-template\node_modules\isexe\index.js:42:5
gyp verb `which` failed     at C:\Users\andersk\sites\forkable-email-template\node_modules\isexe\windows.js:36:5
gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb `which` failed  python2 { Error: not found: python2
gyp verb `which` failed     at getNotFoundError (C:\Users\andersk\sites\forkable-email-template\node_modules\which\which.js:13:12)
gyp verb `which` failed     at F (C:\Users\andersk\sites\forkable-email-template\node_modules\which\which.js:68:19)
gyp verb `which` failed     at E (C:\Users\andersk\sites\forkable-email-template\node_modules\which\which.js:80:29)
gyp verb `which` failed     at C:\Users\andersk\sites\forkable-email-template\node_modules\which\which.js:89:16
gyp verb `which` failed     at C:\Users\andersk\sites\forkable-email-template\node_modules\isexe\index.js:42:5
gyp verb `which` failed     at C:\Users\andersk\sites\forkable-email-template\node_modules\isexe\windows.js:36:5
gyp verb `which` failed     at FSReqWrap.oncomplete (fs.js:154:21)
gyp verb `which` failed   stack:
gyp verb `which` failed    'Error: not found: python2\n    at getNotFoundError (C:\\Users\\andersk\\sites\\forkable-email-template\\node_modules\\which\\which.js:13:12)\n    at F (C:\\Users\\andersk\\sites\\forkable-email-template\\node_modules\\which\\which.js:68:19)\n    at E (C:\\Users\\andersk\\sites\\forkable-email-template\\node_modules\\which\\which.js:80:29)\n    at C:\\Users\\andersk\\sites\\forkable-email-template\\node_modules\\which\\which.js:89:16\n    at C:\\Users\\andersk\\sites\\forkable-email-template\\node_modules\\isexe\\index.js:42:5\n    at C:\\Users\\andersk\\sites\\forkable-email-template\\node_modules\\isexe\\windows.js:36:5\n    at FSReqWrap.oncomplete (fs.js:154:21)',
gyp verb `which` failed   code: 'ENOENT' }
gyp verb check python checking for Python executable "python" in the PATH
gyp verb `which` succeeded python C:\Python37\python.EXE
gyp ERR! configure error
gyp ERR! stack Error: Command failed: C:\Python37\python.EXE -c import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack   File "<string>", line 1
gyp ERR! stack     import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack                                ^
gyp ERR! stack SyntaxError: invalid syntax
gyp ERR! stack
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:289:12)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at maybeClose (internal/child_process.js:962:16)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
gyp ERR! System Windows_NT 10.0.17763
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\andersk\\sites\\forkable-email-template\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\Users\andersk\sites\forkable-email-template\node_modules\node-sass
gyp ERR! node -v v10.13.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\andersk\AppData\Roaming\npm-cache\_logs\2019-01-18T22_17_30_755Z-debug.log