`fsevents` dependency prevents installation

[ranjitjhala]

Hi @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?

[ranjitjhala]

I recently upgraded to Yosemite, I notice this:

fsevents/fsevents#56

Could it be a related issue?

[basarat]

Going through the log : https://gist.github.com/ranjitjhala/1259a624309004498adc#file-atom-typescript-error-L5859-L5870 It seems that its falling over installing grunt-ts which depends on chokidar which depends on fsevents.

The concern is that we only have grunt-ts as a dev dependency (code here) ... and don't expect it to be installed on apm install atom-typescript. Is apm install atom-typescript the command you ran?

[msurdi]

Same error here, just after installing an Atom update, I got a warning about atom-typescript requiring a rebuild. A few seconds after clicking "rebuild" I get the same error.

[msurdi]

Looking at the Atom changelog for 1.0.12:

Atom now ships with Chrome 43 and io.js 2.3.1.

[basarat]

@msurdi / @ranjitjhala can you follow dev machine workflow : https://github.com/TypeStrong/atom-typescript/blob/master/CONTRIBUTING.md#setup-dev-machine to rule out something atom specific crashing the whole workflow. Basically I am curious about manual npm install results 🌹

[msurdi]

@basarat Following the dev setup instructions works fine. To me, it seems that Atom is using its own node version when doing the "rebuild" and not the system wide node I have on my computer. But I don't really now anything about the internals of Atom, so I'm just guessing.

[msurdi]

So, even after manual installation, Atom still complains about the plugin needing a rebuild, and fails again.

[ranjitjhala]

@basarat I can confirm what @msurdi says -- same thing happens on the dev workflow.

(In addition to the above) I tried installing from within atom -- i.e. by clicking on the install button and by doing apm install atom-typescript. In both cases the install succeeds until I open a .ts file, in which case the little bug appears on the bottom right, clicking which leads to the above (and the screenshot on #584).

[Sprechen]

I have the same problem. It seems that with fsevent@1.0.0 this problem can be resolved (webpack/webpack#1435)

[sebilasse]

same here. Package stopped working after updating atom.

[sebilasse]

@Sprechen
Hm - still the same

npm ERR! fsevents@1.0.0 install: node-pre-gyp install --fallback-to-build