`fsevents` dependency prevents installation
See original GitHub issueHi @basarat,
I just re-installed atom
(on mac os) no other packages, and then tried to install atom-typescript
.
I get this error:
Some installed packages could not be loaded because they contain native modules that were compiled for an earlier version of Atom
In more detail
In file included from ../fsevents.cc:6:
In file included from ../node_modules/nan/nan.h:74:
In file included from ../node_modules/nan/nan_new.h:181:
../node_modules/nan/nan_implementation_12_inl.h:172:66: error: too many arguments to function call, expected at most 2, have 4
return v8::Signature::New(v8::Isolate::GetCurrent(), receiver, argc, argv);
~~~~~~~~~~~~~~~~~~ ^~~~~~~~~~
/Users/rjhala/.atom/.node-gyp/.node-gyp/0.30.6/deps/v8/include/v8.h:4515:3: note: 'New' declared here
static Local<Signature> New(
^
1 error 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 (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack at ChildProcess.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:810:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command "node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/rjhala/.atom/packages/atom-typescript/node_modules/grunt-ts/node_modules/chokidar/node_modules/fsevents
gyp ERR! node -v v0.10.30
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok
npm ERR! Darwin 14.5.0
npm ERR! argv "/Applications/Atom.app/Contents/Resources/app/apm/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/Users/rjhala/.atom/.apm/.apmrc" "--userconfig" "/Users/rjhala/.atom/.apmrc" "rebuild" "--target=0.30.6" "--arch=x64"
npm ERR! node v0.10.40
npm ERR! npm v2.13.3
npm ERR! code ELIFECYCLE
npm ERR! fsevents@0.3.5 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the fsevents@0.3.5 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the fsevents package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls fsevents
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/rjhala/.atom/packages/atom-typescript/npm-debug.log
And here is the content of the npm-debug.log
:
https://gist.github.com/ranjitjhala/1259a624309004498adc
Please let me know if I can provide any other information.
Could it be that I have a “stale” fsevents
on my machine?
Shall I wipe the npm database or some such?
Issue Analytics
- State:
- Created 8 years ago
- Comments:28 (6 by maintainers)
Top Results From Across the Web
Any way to avoid fsevents warnings? - Stack Overflow
You can silence the npm WARN upon installation by specifying what types of errors you want to see. You can run npm --logevel=error...
Read more >Visual Studio 2015 - Fixing "Dependencies npm not installed ...
Looks like fsevents is a package that is only used on OSX, so it's an optional dependency that in the case of Windows...
Read more >Problems with npm install after loading project files. - Treehouse
Here is my terminal output when executing npm install for this project. ... DEPENDENCY: fsevents@1.0.14 install: `node-pre-gyp install ...
Read more >npm install error fsevents in Ohter Mac Platforms - Medium
2 — Another solution would be to ignore optional dependencies during the installation (I got it from search the problem on internet) :...
Read more >node npm install --production, dependency error - NodeBB
Each time installation stops on benchpressjs. 2345 warn optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokida...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I resolved this issue by navigating to .atom/packages/atom-typescript
rm -rf node_modules
npm install
and then rebuilding in atom.For what it’s worth, it looks like there was a bug on Atom’s end for rebuilding native modules (see https://github.com/atom/atom/issues/8837) that is resolved in 1.0.15