npm ci在Windows上输出角度8和节点12的错误:node-gyp重建 [英] npm ci outputs errors with angular 8 and node 12 on Windows: node-gyp rebuild

问题描述

我的设置:

• Windows 10
• 适用于Windows的NVM 1.1.7
• 具有npm 6.13.4的节点12.14.1
• Angular 8.2.14和@ angular/cli 8.3.22

只需尝试运行默认的角度模板:

Just trying to run the default angular template:

> npm install -g @angular/cli # this installed the angular version mentioned above
> ng new test # Chose default options for the project
> cd test
> npm ci # lots of error messages

最后一条命令在输出中导致很多错误(但不会使命令失败):

The last command results in lots of errors in the output (but does not fail the command):

> fsevents@1.2.11 install C:\test\node_modules\@angular\compiler-cli\node_modules\fsevents
> node-gyp rebuild


C:\test\node_modules\@angular\compiler-cli\node_modules\fsevents>if not defined npm_config_node_gyp (node "C:\Users\foo\AppData\Roaming\nvm\v12.14.1\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Users\foo\AppData\Roaming\nvm\v12.14.1\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
gyp ERR! find Python
gyp ERR! find Python Python is not set from command line or npm configuration
gyp ERR! find Python Python is not set from environment variable PYTHON
gyp ERR! find Python checking if "python" can be used
gyp ERR! find Python - "python" is not in PATH or produced an error
gyp ERR! find Python checking if "python2" can be used
gyp ERR! find Python - "python2" is not in PATH or produced an error
gyp ERR! find Python checking if "python3" can be used
gyp ERR! find Python - "python3" is not in PATH or produced an error
gyp ERR! find Python checking if the py launcher can be used to find Python 2
gyp ERR! find Python - "py.exe" is not in PATH or produced an error
gyp ERR! find Python checking if Python is C:\Python27\python.exe
gyp ERR! find Python - "C:\Python27\python.exe" could not be run
gyp ERR! find Python checking if Python is C:\Python37\python.exe
gyp ERR! find Python - "C:\Python37\python.exe" could not be run
gyp ERR! find Python
gyp ERR! find Python **********************************************************
gyp ERR! find Python You need to install the latest version of Python.
gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
gyp ERR! find Python you can try one of the following options:
gyp ERR! find Python - Use the switch --python="C:\Path\To\python.exe"
gyp ERR! find Python   (accepted by both node-gyp and npm)
gyp ERR! find Python - Set the environment variable PYTHON
gyp ERR! find Python - Set the npm configuration variable python:
gyp ERR! find Python   npm config set python "C:\Path\To\python.exe"
gyp ERR! find Python For more information consult the documentation at:
gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
gyp ERR! find Python **********************************************************
gyp ERR! find Python
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Python installation to use
gyp ERR! stack     at PythonFinder.fail (C:\Users\foo\AppData\Roaming\nvm\v12.14.1\node_modules\npm\node_modules\node-gyp\lib\find-python.js:307:47)
gyp ERR! stack     at PythonFinder.runChecks (C:\Users\foo\AppData\Roaming\nvm\v12.14.1\node_modules\npm\node_modules\node-gyp\lib\find-python.js:136:21)
gyp ERR! stack     at PythonFinder.<anonymous> (C:\Users\foo\AppData\Roaming\nvm\v12.14.1\node_modules\npm\node_modules\node-gyp\lib\find-python.js:225:16)
gyp ERR! stack     at PythonFinder.execFileCallback (C:\Users\foo\AppData\Roaming\nvm\v12.14.1\node_modules\npm\node_modules\node-gyp\lib\find-python.js:271:16)
gyp ERR! stack     at exithandler (child_process.js:302:5)
gyp ERR! stack     at ChildProcess.errorhandler (child_process.js:314:5)
gyp ERR! stack     at ChildProcess.emit (events.js:223:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
gyp ERR! stack     at onErrorNT (internal/child_process.js:456:16)
gyp ERR! stack     at processTicksAndRejections (internal/process/task_queues.js:81:21)
gyp ERR! System Windows_NT 10.0.18362
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\foo\\AppData\\Roaming\\nvm\\v12.14.1\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\foo\repos\POC\angular\test1\node_modules\@angular\compiler-cli\node_modules\fsevents
gyp ERR! node -v v12.14.1
gyp ERR! node-gyp -v v5.0.5
gyp ERR!

所有错误均与fsevents，node-gyp和python可执行文件无关.没错，我没有安装python，但这不是angular的先决条件.

All errors are related to fsevents, node-gyp and python executable not being found. That's right, I don't have python installed, but it's not a prerequisite for angular.

该命令实际上以0码退出(表示成功-此外，ng build --prod才能成功！)，但是输出中肯定有很多错误.

The command actually exits with a 0 code (indicating success - besides, ng build --prod works after that!) but there surely are a lot of errors in the output.

手动删除node_modules文件夹并运行npm install而不是npm ci会产生短得多且没有任何错误的输出.另外，它不会修改package-lock.json文件，该文件表示已安装相同版本的依赖项.

Deleting the node_modules folder manually and running npm install instead of npm ci produces an output which is a lot shorter and without any error. Also, it does not modify the package-lock.json file, which indicates that the same versions of the dependencies are installed.

这是怎么回事?为什么在使用npm ci时出现这么多错误，而在使用npm install时却没有错误?

What is going on? Why so many errors when using npm ci but none when using npm install?

推荐答案

似乎该错误与此问题和此问题.

Angular间接依赖于fsevents 1.2.11，它不应该在Windows上编译(这是与darwin-OS相关的模块). npm ci有错误，并且忽略了模块package.json中的os字段，因此它仍然尝试编译该模块，这在Windows上失败.

Angular indirectly depends on fsevents 1.2.11, which is not supposed to be compiled on Windows (it's a darwin-OS related module). npm ci is bugged and ignores the os field in the module's package.json, so it tries to compile the module anyway, which fails on Windows.

在以前的角度版本中未发生此错误，因为fsevents 1.2.9是直接从AWS下载二进制文件，而不是对其进行编译.但是由于开发人员无法访问AWS存储桶，导致无法在节点13上安装该模块，他们发布了1.2.11补丁程序以允许节点13的用户安装该软件包.

The error did not occur in previous angular versions because fsevents 1.2.9 was directly downloading binaries from AWS instead of compiling them. But due to a loss of access from the devs to the AWS bucket, leading to the impossibility to install the module on node 13, they released the 1.2.11 patch to allow node 13 users to install the package.

直到npm ci修复和/或fsevents角度更新为2.x，Windows上的解决方法是:

Until npm ci gets fixed and/or fsevents gets updated to 2.x in angular, the workarounds on Windows are either:

• 只需忽略该错误. npm ci退出机密代码0，因为该依赖关系是可选的，因此它不应阻止您的部署脚本(只是将其放慢一点，使其更加冗长).我认为最糟糕的选择是...
• 使用npm install代替npm ci，这将正确处理fsevents依赖项文件的os字段.但这可能会更新您的依赖关系，因此它实际上不适合CI脚本，因为它可以更改版本化的文件，并且不会产生可重复的输出.
• 在依赖文件中将fsevents模块版本锁定为1.2.9，而不是1.2.11，以便npm ci下载二进制文件而不是编译它们.使用节点13时，此操作将无效，因为此版本的节点没有二进制文件可供下载.另外，我找不到如何更新package.json文件来做到这一点的方法(这对我不起作用).
• 使用npm ci --no-optional.不幸的是，由于npm ci中的还有另一个错误，该操作无法正常工作. li>

• Just ignore the error. npm ci exits wit code 0 because the dependency is optional, so it should not block your deployment script (just slow it down a bit and make it more verbose). The least bad option in my opinion...
• Use npm install instead of npm ci, which will correctly process the os field of fsevents dependencies file. But this will potentially update your dependencies, so it is not really suitable for CI scripts, as it can change versioned files, and does not produce a repeatable output.
• Lock the fsevents module version to 1.2.9 instead of 1.2.11 in your dependencies file, so that npm ci downloads the binaries instead of compiling them. This won't work when using node 13, as there are no binaries to download for this version of node. Also, I could not find how one should update the package.json file to do that (this didn't work for me).
• Use npm ci --no-optional. Unfortunately this doesn't work, because of yet another bug in npm ci.

这篇关于npm ci在Windows上输出角度8和节点12的错误:node-gyp重建的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！