<p>yarn 安装 fsevents 失败，而 npm 成功</p>

创建于 2018-06-10 · 43评论 · 资料来源: yarnpkg/yarn

*在创建问题之前，请确保您使用的是最新版本的纱线。*

您要请求功能还是报告错误？

漏洞

目前的行为是什么？

yarn安装fsevents (404s) 失败，而npm成功

如果当前行为是错误，请提供重现步骤。

用`yarn`

❯ git clone [email protected]:minusfive/ember-cli-sass-variables-export.git
❯ cd ember-cli-sass-variables-export
❯ yarn
yarn install v1.7.0
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
[3/5] 🚚  Fetching packages...
[-------------------------------------------------------------------------------------------------------------------------------------------------------] 0/1048(node:5246) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[4/5] 🔗  Linking dependencies...
warning " > [email protected]" has unmet peer dependency "eslint@>=3.1.0".
[5/5] 📃  Building fresh packages...
[-/3] ⠁ waiting...
[2/3] ⠂ fsevents
warning Error running install script for optional dependency: "/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents: Command failed.
Exit code: 1
Command: node install
Arguments:
Directory: /Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents
Output:
node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using [email protected]
node-pre-gyp info using [email protected] | darwin | x64
node-pre-gyp info check checked for \"/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node\" (not found)
node-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.3/fse-v1.1.3-node-v64-darwin-x64.tar.gz
node-pre-gyp http 404 https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.3/fse-v1.1.3-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.3/fse-v1.1.3-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v64 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp http 404 status code downloading tarball https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.3/fse-v1.1.3-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Tried to download(undefined): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.1.3/fse-v1.1.3-node-v64-darwin-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v64 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp http Connection closed while downloading tarball file
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gyp info ok
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gyp info ok
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gyp http GET https://nodejs.org/download/release/v10.4.0/node-v10.4.0-headers.tar.gz
gyp http GET https://nodejs.org/download/release/v10.4.0/node-v10.4.0-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v10.4.0/node-v10.4.0-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v10.4.0/node-v10.4.0-headers.tar.gz
gyp http GET https://nodejs.org/download/release/v10.4.0/SHASUMS256.txt
gyp http GET https://nodejs.org/download/release/v10.4.0/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v10.4.0/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v10.4.0/SHASUMS256.txt
gyp info spawn /usr/bin/python
gyp info spawn args [ '/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/minusfive/.node-gyp/10.4.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/minusfive/.node-gyp/10.4.0',
gyp info spawn args   '-Dnode_gyp_dir=/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/Users/minusfive/.node-gyp/10.4.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info spawn /usr/bin/python
gyp info spawn args [ '/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/minusfive/.node-gyp/10.4.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/minusfive/.node-gyp/10.4.0',
gyp info spawn args   '-Dnode_gyp_dir=/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/Users/minusfive/.node-gyp/10.4.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info ok
gyp info ok
gyp info it worked if it ends with ok
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gyp info using [email protected]
gyp info using [email protected] | darwin | x64
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
  SOLINK_MODULE(target) Release/.node
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  CXX(target) Release/obj.target/fse/fsevents.o
In file included from ../fsevents.cc:6:
../../nan/nan.h:839:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:171:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED(\"Use MakeCallback(..., async_context)\",
^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../fsevents.cc:6:
../../nan/nan.h:854:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:164:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED(\"Use MakeCallback(..., async_context)\",
^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../fsevents.cc:6:
../../nan/nan.h:869:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:157:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED(\"Use MakeCallback(..., async_context)\",
^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../fsevents.cc:6:
../../nan/nan.h:839:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:171:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED(\"Use MakeCallback(..., async_context)\",
^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../fsevents.cc:6:
../../nan/nan.h:854:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:164:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED(\"Use MakeCallback(..., async_context)\",
^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../fsevents.cc:6:
../../nan/nan.h:869:18: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return node::MakeCallback(
                 ^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:157:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED(\"Use MakeCallback(..., async_context)\",
^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../fsevents.cc:6:
../../nan/nan.h:1648:31: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return scope.Escape(node::MakeCallback(
                              ^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:171:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED(\"Use MakeCallback(..., async_context)\",
^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../fsevents.cc:6:
../../nan/nan.h:1648:31: warning: 'MakeCallback' is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
    return scope.Escape(node::MakeCallback(
                              ^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:171:1: note: 'MakeCallback' has been explicitly marked deprecated here
NODE_DEPRECATED(\"Use MakeCallback(..., async_context)\",
^
/Users/minusfive/.node-gyp/10.4.0/include/node/node.h:88:20: note: expanded from macro 'NODE_DEPRECATED'
    __attribute__((deprecated(message))) declarator
                   ^
In file included from ../fsevents.cc:85:
../src/methods.cc:14:12: warning: 'Call' is deprecated [-Wdeprecated-declarations]
  handler->Call(3, argv);
           ^
../../nan/nan.h:1567:3: note: 'Call' has been explicitly marked deprecated here
  NAN_DEPRECATED inline v8::Local<v8::Value>
  ^
../../nan/nan.h:98:40: note: expanded from macro 'NAN_DEPRECATED'
# define NAN_DEPRECATED __attribute__((deprecated))
                                       ^
In file included from ../fsevents.cc:85:
../src/methods.cc:14:12: warning: 'Call' is deprecated [-Wdeprecated-declarations]
  handler->Call(3, argv);
           ^
../../nan/nan.h:1567:3: note: 'Call' has been explicitly marked deprecated here
  NAN_DEPRECATED inline v8::Local<v8::Value>
  ^
../../nan/nan.h:98:40: note: expanded from macro 'NAN_DEPRECATED'
# define NAN_DEPRECATED __attribute__((deprecated))
                                       ^
5 warnings generated.
5 warnings generated.
  SOLINK_MODULE(target) Release/fse.node
rm: cannot remove './Release/.deps/Release/obj.target/fse/fsevents.o.d.raw': No such file or directory
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12)
gyp ERR! System Darwin 17.6.0
gyp ERR! command \"/usr/local/Cellar/node/10.4.0/bin/node\" \"/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-gyp/bin/node-gyp.js\" \"build\" \"--fallback-to-build\" \"--module=/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node\" \"--module_name=fse\" \"--module_path=/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64\"
gyp ERR! cwd /Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents
gyp ERR! node -v v10.4.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/Cellar/node/10.4.0/bin/node /Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node --module_name=fse --module_path=/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:961:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5)
node-pre-gyp ERR! System Darwin 17.6.0
node-pre-gyp ERR! command \"/usr/local/Cellar/node/10.4.0/bin/node\" \"/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp\" \"install\" \"--fallback-to-build\"
node-pre-gyp ERR! cwd /Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents
node-pre-gyp ERR! node -v v10.4.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.39
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/Cellar/node/10.4.0/bin/node /Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node --module_name=fse --module_path=/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64' (1)
  COPY /Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  TOUCH Release/obj.target/action_after_build.stamp
✨  Done in 157.31s.

用`npm`

❯ rm -rf node_modules
❯ npm install

> [email protected] install /Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents
> node install

[fsevents] Success: "/Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile

> [email protected] install /Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-sass
> node scripts/install.js

Cached binary found at /Users/minusfive/.npm/node-sass/4.9.0/darwin-x64-64_binding.node

> [email protected] postinstall /Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/spawn-sync
> node postinstall


> [email protected] postinstall /Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-sass
> node scripts/build.js

Binary found at /Users/minusfive/dev/oss/ember-cli-sass-variables-export/node_modules/node-sass/vendor/darwin-x64-64/binding.node
Testing binary
Binary is fine
added 1317 packages from 645 contributors and audited 40932 packages in 32.386s

什么是预期行为？

它应该工作吗？

请提及您的 node.js、yarn 和操作系统版本。

❯ node -v
v10.4.0

❯ npm -v
6.1.0

❯ yarn -v
1.7.0

❯ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.13.5
BuildVersion:   17F77

triaged

资料来源

minusfive

👍45 ❤8

最有用的评论

我在Node 10.4.1上也遇到了这个问题。

更新：事实证明我们使用的 Webpack 版本取决于与Node ^10不兼容的旧版本fsevents Node ^10 。

尝试运行yarn upgrade 。

jadchaar 于 2018-06-14

👍98 ❤23 🎉20 🚀15 😄9

所有43条评论

这不是纱线。它是 AWS 从通过 fsevents 运行的安装脚本之一为您提供 404。看起来它通过 npm 完成，因为它被缓存了。如果你用 Yarn 再试一次，如果这是一个临时的服务器问题，它可能会通过。

如果没有，那么如果您清除 npm 缓存并重试，那也会失败。

BYK 于 2018-06-10

我清除了我的纱线和节点缓存，但仍然出现此错误，纱线 1.6.0，节点 10.1.0。

justin808 于 2018-06-13

👍3

我在Node 10.4.1上也遇到了这个问题。

更新：事实证明我们使用的 Webpack 版本取决于与Node ^10不兼容的旧版本fsevents Node ^10 。

尝试运行yarn upgrade 。

jadchaar 于 2018-06-14

👍98 ❤23 🎉20 🚀15 😄9

我也有这个问题，但只在我几个月前用yarn create react-app [dir name]设置的目录中。

如果我创建一个新目录，即为一个不同的项目，那么我没有问题。

我正在使用node 10.4.1 npm 6.1.0 yarn 1.7.0

我试过运行yarn upgrade但它触发了相同的错误 w/fsevents。

有人有其他想法吗？

jacksonhardy 于 2018-06-18

@sisterjones我在使用 CRA 的 Mac 上遇到了同样的问题，这让我发疯（节点 10.4.1）。虽然它适用于 Windows，但我在 Windows 中有 Node 9.11.1

编辑：我降级到 Node 9.11.12，现在一切正常。希望尽快修复此问题

esausilva 于 2018-06-19

👍3

节点 10.5.0 在 MacOS 上的相同问题

MaxGraey 于 2018-06-25

👍12

节点 10.6.0 的相同问题（macOs mojave beta 2）

wilomgfx 于 2018-07-11

只需将节点降级到 LTS 8.11.3 即可正常工作。

每个低于 10 的 nodejs 版本都应该可以工作。

xuqingkuang 于 2018-07-18

我在将 Ember 项目升级到需要 node 10+ 的 3.2 版时遇到了这个问题。唯一有帮助的是yarn upgrade 。

joshkg 于 2018-07-19

👍23 🎉12 ❤7 🚀2

使用节点 8.11 固定

regiondavid 于 2018-08-31

👎11

最新的 Yarn 版本修复了这个问题。更新后我没有遇到过这个问题，现在我正在运行 Node 10.x

esausilva 于 2018-08-31

我无法运行 yarn upgrade 因为它说：

错误过时的锁文件。请运行yarn install并重试。

运行 yarn install 时，它说：

错误 /Users/username/Programming/github.com/projectname/node_modules/node-zopfli: 命令失败。
退出代码：1

接缝就像是我不可能完成的任务

Macilias 于 2018-09-03

😄1

@Macilias您可以删除锁定文件，当运行yarn install时，纱线将重新创建它

esausilva 于 2018-09-04

虽然是这样，但一旦文件被删除，yarn 就无法重新创建它，因此项目处于不可用状态......我们无法弄清楚如何更新它以进入可用状态。

Macilias 于 2018-09-04

我已经清除了缓存，效果很好。试试yarn cache clean

ghost 于 2018-09-25

👍7 🚀2 🎉1

与 Mojave OS 上的yarn cache clean相同。 😕
输出：

...
gyp ERR! cwd /Users/username/.../app/node_modules/fsevents
gyp ERR! node -v v10.12.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
...

maximelafarie 于 2018-10-26

👍3

首先尝试运行yarn global add node-gyp ，然后尝试安装 fsevents。顺便提一句。你用的是哪个版本的纱线？在最近的版本中，这应该不是必需的。

BYK 于 2018-10-26

我有同样的问题，就像@maximelafarie
尝试运行yarn global add node-gyp并没有救我。 @BYK

yarn version :1.2.1
node version :v10.13.0
npm version :6.4.1
macOS version : Mojave

编辑
对于那些和我一样有同样问题的人，我必须降级节点版本以跳过重新安装fsevents 。所以我要粘贴我工作区的最终环境

yarn version :1.2.3
node version :8.12.0

underwindfall 于 2018-10-30

👍2

我的工作如下 -

rm yarn.lock
yarn cache clean
yarn install

shrinathaithal 于 2018-11-01

👍63 🎉21 🚀14 ❤14 👎9 😄7

与@maximelafarie相同的错误， yarn global add一些包带有fsevents ，但yarn cache clean成功。

纱线 1.12.1
节点 11.0.0
macOS 10.14 莫哈韦沙漠

编辑
这个问题似乎可以通过运行yarn global add node-gyp然后yarn global remove node-gyp ......我不确定发生了什么，无论如何一切对我来说都没有错误😭

yuhr 于 2018-11-03

👍10 🎉4 😕2 🚀1

这个问题也发生在我身上。

纱线 1.12.1
节点 11.0.0
macOS 1.14 莫哈韦沙漠。

上述修复对我不起作用。

evannorstrand 于 2018-11-03

👍1

我也是：

纱线 1.12.3
节点 v11.1.0
macOS 10.14.1

上述修复对我不起作用。

ambroisemaupate 于 2018-11-13

👍3

我也是....为什么这个问题被关闭了？

09:13:23 $ node -v
v11.2.0
09:18:10 $ yarn -v
1.12.3
09:18:12 $ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.13.6
BuildVersion:   17G65

leegee 于 2018-11-30

👍3

就我而言，使用 pyenv 将 python 降级到 2.7 很有帮助。

node-gyp 需要 python 2.7，而不是 3.x。

rld2drkw 于 2018-12-02

👍1

在带有版本的 Mac OS X 上：

$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.13.6
BuildVersion:   17G3025
$ node -v
v11.12.0
$ yarn -v
1.15.2

以下帮助（并且是 npm 之前成功）：

# xcode was erroring with brew
sudo xcode-select --switch /Applications/Xcode.app
sudo xcodebuild -license accept

# fresh new node modules
rm -rf node_modules

# solution <strong i="9">@shrinathaithal</strong> (these commands alone did not help though)
rm yarn.lock
yarn cache clean
yarn install

tomsiwik 于 2019-03-20

👍20 🎉11 🚀10 ❤8 😄5 👀4

通过将节点的版本从最新更改为 lts，我解决了完全相同的错误。

$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.14.4
BuildVersion:   18E227
$ npm -v
6.4.1
$ yarn -v
1.15.2
$ node -v
v12.0.0

$ sudo n lts
$ node -v
v10.15.3

$ create-react-app my-app

kenjioi 于 2019-04-25

刚刚在我的 Mac 上使用 Node v12.1.0 遇到了类似的问题。使用$ yarn upgrade修复它。我认为关键是从 fsevents v1.2.8 更新到 v1.2.9。

difosfor 于 2019-05-03

我遇到了与运行以下相同的问题：

> sw_vers
ProductName:    Mac OS X
ProductVersion: 10.14.4
BuildVersion:   18E226
> node -v
v12.1.0

运行yarn cache clean然后在 v10.15.3 使用 Node.js 的 LTS 版本而不是当前版本修复它。

我是nvm来处理多个 Node.js 版本。

conatus 于 2019-05-07

👍4

通过将节点从v12.2.0降级到 LTS v10.15.3在这里修复了另一个

mmontag 于 2019-05-12

最近 fsevents 出现了一个问题，导致它与 Node 12 不兼容。这个问题已在 fsevents v1.2.9 中解决并发布。如果您有依赖 fsevents 的依赖项，您可以使用分辨率告诉 Yarn 为每个依赖项使用 1.2.9 版：

将此添加到您的package.json文件，然后重新运行yarn （或yarn install ）：

"resolutions": {
  "fsevents": "1.2.9"
}

coreyward 于 2019-05-13

👍46 🎉11 🚀6 ❤6 😕1

纱线升级解决了我的问题。

rolandoalvarado 于 2019-05-30

请注意，由于 #6834 错误，Yarn 会将resolutions （如@coreyward 建议）中列出的包视为非可选包。由于该错误，您的构建可能会在 macOS 上成功，但在 Linux 上会失败。

byzyk 于 2019-07-08

👍2

我最近遇到了这个问题， yarn upgrade确实解决了这个问题。谢谢！

aindong 于 2019-07-09

@aindong你看到上面的评论了吗？

请注意，由于 #6834 错误，Yarn 会将resolutions （如@coreyward 建议）中列出的包视为非可选包。由于该错误，您的构建可能会在 macOS 上成功，但在 Linux 上会失败。

您可以在 Mac 上执行yarn upgrade ，这将安装fsevents ，但是当您部署到fsevents不可用的 Linux 服务器时（它是 macOS 特定的）它会失败。

coreyward 于 2019-07-09

如果您仍然对fsevents有问题，您可能需要升级您正在使用的软件包。他们可能有旧的依赖关系，最终使用旧版本的fsevents 。就我而言，它是nodemod -> yarn upgrade nodemon

如何找到它们：

yarn list
向后搜索所有出现的fsevents
更新这些软件包（最好是最新版本）。 yarn upgrade <package>
删除本地 node_modules rm -rf node_modules
干净的纱线缓存yarn cache clean
重新安装软件包yarn

egel 于 2019-08-01

@egel这fsevents引用为依赖项的依赖项将其声明~> 0.2.7或>= 0.2.7 ，这允许您在安装版本0.2.9同时仍然满足要求。因此，使用分辨率的解决方案，它允许您让 Yarn _resolve_ 对特定版本的依赖声明（例如fsevents ~> 0.2.7或fsevents ）。

需要注意的是，这对大多数依赖项都非常有效，但是因为fsevents是特定于平台的，并且以前版本的 Yarn 不允许分辨率是可选的，当 Yarn 将在不使用fsevents的环境中运行时yarn install ，然后提交 _only_ 您的yarn.lock文件并丢弃分辨率package.json文件中的声明。这将导致使用正确版本的fsevents ，但由于未使用分辨率，因此不会破坏可选标志。

在任何情况下，当您没有损坏包的问题时，运行rm -rf node_modules和yarn cache clean是无效的。通过网络重建整个缓存也很慢，不建议不必要地这样做。

coreyward 于 2019-08-01

👍3

我通过将节点版本更改为 10.2.1、纱线 1.21.1 解决了node-pre-gyp ERR! not ok ，现在工作正常！

andreluisjunqueira 于 2020-01-16

不知道还有没有人遇到这个问题。我解决了它
yarn install --check-files
我不得不这样做几次

我是在 OSX 10.13 High Sierra 上做的

chuxolatouz 于 2020-01-17

❤2

对我有用：

yarn upgrade
revert changes in package.json (if needed for your situation)
rm -rf node_modules
rm yarn.lock
yarn
commit newly created lock file

bmorrical-ICC 于 2020-02-03

👎7

它对我有用xcode-select --install

jmlavoier 于 2020-03-01

👎3

就我而言，由于我有 Babel，我无法使用：

"resolutions": {
  "**/**/fsevents": "^1.2.9"
}

由于使用不同版本的多个嵌套依赖项。

但我成功地使用了：

  "resolutions": {
    "**/**/chokidar": "^2.1.8"
  }

粗略地说，Babel 团队希望保持与 Node 6 的兼容性，这就是为什么它仍然使用旧的fsevents ，但他们计划在 Babel v8 中迁移。

希望能帮到你🥰

sneko 于 2020-06-26

👍2

我通过删除package-lock.json并重新运行npm install解决了这个问题。

JeffreyCA 于 2020-07-07

👎2

不知道还有没有人遇到这个问题。我解决了它
yarn install --check-files
我不得不这样做几次
我是在 OSX 10.13 High Sierra 上做的

这为我解决了！我也不得不运行它几次。
谢谢

dario-pon 于 2020-07-27

此页面是否有帮助？

0 / 5 - 0 等级

<p>yarn 安装 fsevents 失败，而 npm 成功</p>

用yarn

用npm

最有用的评论

所有43条评论

相关问题

用`yarn`

用`npm`