fsevents: Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.4/fse-v1.2.4-node-v67-darwin-x64.tar.gz

There was an error while installing node modules using npm install Node: v11.2.0 react-native: 0.57.8

Log:

MacFour:~ four$ cd /Users/four/Desktop/ReactXPNavDemo 
MacFour:ReactXPNavDemo four$ npm install reactxp-navigation

> fsevents@1.2.4 install /Users/four/Desktop/ReactXPNavDemo/node_modules/fsevents
> node install

node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.4/fse-v1.2.4-node-v67-darwin-x64.tar.gz 
node-pre-gyp WARN Pre-built binaries not found for fsevents@1.2.4 and node@11.2.0 (node-v67 ABI, unknown) (falling back to source compile with node-gyp) 
  SOLINK_MODULE(target) Release/.node
clang: warning: using sysroot for 'iPhoneSimulator' but targeting 'MacOSX' [-Wincompatible-sysroot]
  CXX(target) Release/obj.target/fse/fsevents.o
clang: warning: using sysroot for 'iPhoneSimulator' but targeting 'MacOSX' [-Wincompatible-sysroot]
../fsevents.cc:63:6: warning: field 'async_resource' will be initialized after
      field 'lockStarted' [-Wreorder]
   : async_resource("fsevents:FSEvents"), lockStarted(false) {
     ^
In file included from ../fsevents.cc:81:
../src/thread.cc:36:25: error: unknown type name 'ConstFSEventStreamRef'
void HandleStreamEvents(ConstFSEventStreamRef stream, void *ctx, size_t ...
                        ^
../src/thread.cc:36:108: error: unknown type name 'FSEventStreamEventFlags'
  ...stream, void *ctx, size_t numEvents, void *eventPaths, const FSEventStre...
                                                                  ^
../src/thread.cc:36:152: error: unknown type name 'FSEventStreamEventId'
  ...*eventPaths, const FSEventStreamEventFlags eventFlags[], const FSEventSt...
                                                                    ^
../src/thread.cc:54:3: error: unknown type name 'FSEventStreamContext'
  FSEventStreamContext context = { 0, ctx, NULL, NULL, NULL };
  ^
../src/thread.cc:56:3: error: unknown type name 'FSEventStreamRef'
  FSEventStreamRef stream = FSEventStreamCreate(NULL, &HandleStreamEvent...
  ^
../src/thread.cc:56:98: error: use of undeclared identifier
      'kFSEventStreamEventIdSinceNow'
  ...&HandleStreamEvents, &context, fse->paths, kFSEventStreamEventIdSinceNow...
                                                ^
1 warning and 6 errors generated.
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 (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:254:12)
gyp ERR! System Darwin 17.7.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/Users/four/Desktop/ReactXPNavDemo/node_modules/fsevents/lib/binding/Release/node-v67-darwin-x64/fse.node" "--module_name=fse" "--module_path=/Users/four/Desktop/ReactXPNavDemo/node_modules/fsevents/lib/binding/Release/node-v67-darwin-x64" "--napi_version=3" "--node_abi_napi=napi"
gyp ERR! cwd /Users/four/Desktop/ReactXPNavDemo/node_modules/fsevents
gyp ERR! node -v v11.2.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok 
node-pre-gyp ERR! build error 
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/four/Desktop/ReactXPNavDemo/node_modules/fsevents/lib/binding/Release/node-v67-darwin-x64/fse.node --module_name=fse --module_path=/Users/four/Desktop/ReactXPNavDemo/node_modules/fsevents/lib/binding/Release/node-v67-darwin-x64 --napi_version=3 --node_abi_napi=napi' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/four/Desktop/ReactXPNavDemo/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:978:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
node-pre-gyp ERR! System Darwin 17.7.0
node-pre-gyp ERR! command "/usr/local/bin/node" "/Users/four/Desktop/ReactXPNavDemo/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /Users/four/Desktop/ReactXPNavDemo/node_modules/fsevents
node-pre-gyp ERR! node -v v11.2.0
node-pre-gyp ERR! node-pre-gyp -v v0.10.0
node-pre-gyp ERR! not ok 
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/four/Desktop/ReactXPNavDemo/node_modules/fsevents/lib/binding/Release/node-v67-darwin-x64/fse.node --module_name=fse --module_path=/Users/four/Desktop/ReactXPNavDemo/node_modules/fsevents/lib/binding/Release/node-v67-darwin-x64 --napi_version=3 --node_abi_napi=napi' (1)
npm WARN react-native-windows@0.57.0-rc.0 requires a peer of react@16.5.0 but none is installed. You must install peer dependencies yourself.
npm WARN reactxp@1.5.0 requires a peer of react-native@^0.55.0 but none is installed. You must install peer dependencies yourself.
npm WARN reactxp@1.5.0 requires a peer of react-native-windows@^0.55.0-rc.0 but none is installed. You must install peer dependencies yourself.
npm WARN reactxp-navigation@1.5.0 requires a peer of react-native@^0.55.0 but none is installed. You must install peer dependencies yourself.
npm WARN reactxp-navigation@1.5.0 requires a peer of react-native-windows@^0.54.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 install: `node install`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

+ reactxp-navigation@1.5.0
added 3 packages from 34 contributors and audited 46430 packages in 18.037s
found 11 vulnerabilities (9 low, 2 moderate)
  run `npm audit fix` to fix them, or `npm audit` for details

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 57
Comments: 39 (5 by maintainers)

Commits related to this issue

Added fix for fsevents in package.json https://github.com/fsevents/fsevents/issues/246#issuecomment-505516700 Temporary fix for serviceworker security issue (i.e. registered the serviceworker) Re-adde... — committed to jungshadow/yfpp by jungshadow 4 years ago

Most upvoted comments

I think you just to need to remove package-lock.json and try it again.

+245

garyrojas on Aug 7, 2019

faced similar issue, and after adding below code to package.json re-run npm install/ yarn install

"resolutions": {
		"**/**/node-gyp": "5.0.0"
}

Hope this helps

+48

techdiary on Jun 25, 2019

Solve the problem by uninstalling fsevents, and install fsevents@1.2.9 and delete package-lock.json and npm install. Thank you! @faq885

+44

iamlockelightning on Jun 28, 2019

I solved the above issue by removing node_modules and .lock files and installing the dependencies like following:

rm -rf node_modules yarn.lock package-lock.json
PYTHON=python2 yarn install

+39

ziishaned on Feb 17, 2020

try this: restart your computer

+33

jackgreentemp on Feb 29, 2020

Im using MacBook Pro and using the latest Xcode and Node version.

This is what worked for me:

rm -rf node_modules yarn.lock package-lock.json
npm install

+11

goddar on Mar 30, 2020

faced similar issue, and after adding below code to package.json re-run npm install/ yarn install
"resolutions": {
		"**/**/node-gyp": "5.0.0"
}
Hope this helps

2020 MacBook and XCODE updated and I faced same problem, this solution saved my day. Thanks

iradofurioso on May 12, 2020

I think you just to need to remove package-lock.json and try it again.

work for me.

everlose on Nov 22, 2019

i fixed this problem by upgrading “react-scripts” to latest version “^3.4.3”. you can try >“npm audit fix --force” to check if any other issues.

macSantosh on Sep 13, 2020

@iamlockelightning doing yarn add fsevents solved it to me, also you can research to add a restriction to the package json, it also solved the problem but i don’t have now what code i added

yarn add fsevents simple as, solved 👍

chrisaddams on Dec 21, 2019

After trying the above methods to no avail, I checked the information about the project files used by node-gyp in the node environment to generate different compilers for different platforms, so I solved it by npm install -g node-gyp !

Travelguest on May 28, 2021

I can confirm that deleting your package-lock.json and node_modules/ and then npm i everything helped remove these errors as well.

hectorleiva on Feb 17, 2020

“resolutions”: { “//node-gyp”: “5.0.0” }

Thanks so much mate!! you did the trick! @techdiary!!

faq885 on Jun 26, 2019

I think you just to need to remove package-lock.json and try it again.

Thank you @garyrojas that worked for me!

If anyone just updated their mac osx to Catalina, try this first before reinstalling Xcode or command line tools or nodejs.

Snesi on Jan 30, 2020

@iamlockelightning doing yarn add fsevents solved it to me, also you can research to add a restriction to the package json, it also solved the problem but i don’t have now what code i added

faq885 on Jun 27, 2019

My xcode seems to work fine. I tried to use npm update and then, npm install Then the problem is solved.

FuyaoLi2017 on Apr 18, 2020

The actual root cause of this issue is that the binary files for the version you are trying to fetch have been removed from AWS (looks like the binary files are hosted there).

So, if you try to install your packages when you have a version of fsevents that does not have the binary files on AWS, you get this issue.

The easiest way to fix this issue is indeed removing yarn.lock or package-lock.json file depending on what package manager you are using, yarn or npm. However, you might not want to do this as this will cause all your dependencies and their sub dependencies to be upgraded to a possible newer version based on semantic versioning. And this might cause some incompatibility issues between some other packages. This may not happen in most cases, but there is still a chance that it might.

So, perhaps, a better way to fix this issue is to find that specific version in the lock file and remove the whole block and then install packages. Since there is no record for that version of the package, the package manager will fetch a proper version and update your lock file. Although it is not recommended to modify your lock file manually, it is safe to make such moves when you know what you are doing.

Examples of how to do that for each lock file are as the following:

yarn.lock yarn-lock-fix-fsevents

package-lock.json (Here I had to do it for another package but that does not change anything. You just need to find the package you want to remove) package-lock-json-fix-core-js

In the above screenshots, we removed the block on the left and installed packages. After the installation we got the block on the right.

Everything above is valid for any package that may have the same issue.

cahitihac on Apr 25, 2022

try this: restart your computer

Thanks @jackgreentemp worked for me

makarkotlov on Feb 29, 2020

The 404 means there’s no precompiled binary for your Node.js version. The install script then tries to build from source but in order for that to succeed you need to have Xcode or the Command Line Tools installed with the right SDK.

bnoordhuis on Dec 29, 2018

From the looks of it you’re using the wrong Xcode SDK. You need the macOS SDK, not the iPhone one. If you have multiple SDKs installed, you can switch between them with xcode-select.

bnoordhuis on Dec 28, 2018

Deleting node modules folder and package-lock.json works for me. I have to use node 11.0.0 with N installer.

CarlosMayoralMX on Apr 1, 2021

try this: restart your computer

Fixed for me on the second reboot after trying other commands above. So maybe the combination of those commands and reboots finally helped.

lovetofail on Mar 18, 2020

Node.js v8.x and v10.x. I don’t know if we have binaries for v6.x or v11.x.

bnoordhuis on Dec 29, 2018

I have the some question.

vvpvvp on Dec 29, 2018