fsevents dependency not available on linux

[oli-obk]

When running npm install in ui/frontend i get the following error:

npm ERR! notsup Unsupported

npm ERR! notsup Not compatible with your operating system or architecture: fsevents@1.0.12
npm ERR! notsup Valid OS:    darwin
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   linux
npm ERR! notsup Actual Arch: x64

As mentioned in the github repos of fsevents fsevents/fsevents#134, fsevents is OSX only. I'm not sure how to proceed :)

[killercup]

@oli-obk delete the npm-shrinkwarp file

[oli-obk]

that works... why is it even there?

[killercup]

It's npm's version of Cargo.lock. Sadly, it's pretty simple and doesn't have any knowledge of platform-dependent dependencies, so it always represents the exact set of dependencies of the machine it was generated on.

[oli-obk]

Ah hmm... unfortunate. Thanks for the explanation

[shepmaster]

Unfortunate indeed! That also means that it's likely I've broken my own deployment as I develop on OS X and deploy on Linux.

I make no claims to being a good JS developer, so it's entirely possible that I've borked the shrinkwrap file (I know it's seemingly rewritten itself multiple times).

[shepmaster]

@oli-obk could you add your node and npm versions?

In my development environment, I have

$ node --version
v6.3.0
$ npm --version
3.10.3

(it appears I have the same versions in production)

[oli-obk]

yea... my versions are "a little" older

$ node --version
v4.3.1
$ npm --version
1.4.21

[shepmaster]

@oli-obk I think newer versions of npm downgraded the error to a warning. Are you able to give upgrading a shot and see how it plays out?

[oli-obk]

unfortunately node on debian testing is on v4. experimental is on 6.0, so I'll wait until that trickles downstream.

[shepmaster]

I'll wait until that trickles downstream.

That's fine! If you want to, you can also upgrade npm separately: npm install -g npm. But if that's also managed by your system package manager I understand.