Fsevents: Support for Node v6

Created on 8 Jun 2016  路  10Comments  路  Source: fsevents/fsevents

Already said here: https://github.com/strongloop/fsevents/issues/122#issuecomment-221005180
Now I understood better:
From Electron v.1.1.0, they use Node v.6.1.0 (https://github.com/electron/electron/releases/tag/v1.1.0)
Now they are at Electron: 1.2.1 Node: 6.1.0 (http://electron.atom.io/)

When I run, first it don't find the needed FSEvents package.
In node_modules/fsevents/lib/binding/Release, for the file fse.node, it exists node-v47-darwin-x64, but it needs node-v48-darwin-x64 (for node v6 I guess).
If I try to rename (copy/paste) into ...v48... it sais, obviously, into console.log : Error: Module version mismatch. Expected 48, got 47.

So I guess fsevents don't yet support node v6?

Or am I doing something wrong?
I tried npm rebuild fsevents --build-from-source and npm rebuild fsevents --update-binary. All methods will download only v47, not v48.

Most helpful comment

@es128 it's released

All 10 comments

fsevents supports node v6. There are no prebuilt binaries yet but building from source should work.

I don't think prebuilt binaries would have helped in your case though. Electron says it's ABI compatible with v6 here (NODE_MODULE_VERSION == 48) but v6 ships with V8 5.0 whereas electron ships 5.1. That's not going to work.

+1

I'm waiting for node-pre-gyp 0.6.29 to actually be published (https://github.com/mapbox/node-pre-gyp/issues/218), then will publish a new fsevents with it.

Should help with node v6.1.0 - although electron builds seem to still be complicated in some cases.

thanks

@es128 it's released

Looks like this has been pulled - can fsevents be version bumped so it can be npm installed? Don't mean to step on any toes, sorry if I am. Just excited to use Node 6 so I can get rid of babel and can't without this :(

+1

Just published 1.0.13 with the latest node-pre-gyp. Sorry for the delay.

I'm getting Module version mismatch. Expected 49, got 46 with these versions:

  • node v6.3.0
  • electron v1.3.3
  • fsevents v1.0.14
  • node-pre-gyp v0.6.29

I ran...
./node_modules/node-pre-gyp/bin/node-pre-gyp install --build-from-source
... from within Electron.

These bindings exist within fsevents/lib/binding/Release:

  • electron-v1.3-darwin-x64
  • node-v11-darwin-x64
  • node-v46-darwin-x64
  • node-v47-darwin-x64

Any advice on getting v49 instead of v46?

@aleclarson I'm going to guess that you install using node, then try to run the result in electron?

You will have to consult the node-pre-gyp documentation on how to override the node_abi variable because auto-detection is going to fail in that scenario. npm install fsevents --runtime=electron may do the trick but you will have to check that.

Was this page helpful?
0 / 5 - 0 ratings