npm Mac vs npm Linux keep fighting over fsevents package

[ffxsam]

I'm opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don't understand.
• Other (see below for feature requests):

What's going wrong?

I have a project that I started on macOS, that has fsevents in package.json and package-lock.json. When I work on this project on Ubuntu and run npm i, it removes fsevents from package-lock.json. I'm not sure if this is intended, but this would ultimately result in macOS & Ubuntu fighting by constantly adding/removing fsevents whenever npm i is run.

supporting information:

• npm -v prints: 5.4.2
• node -v prints: v4.8.2
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: macOS & Linux
• Network issues:
  • Geographic location where npm was run:
  • I use a proxy to connect to the npm registry.
  • I use a proxy to connect to the web.
  • I use a proxy when downloading Git repos.
  • I access the npm registry via a VPN
  • I don't use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

[bgoscinski]

Probably dup of #18135

[dennisreimann]

fyi: This is part of the recent v5.6.0 release.

[Splaktar]

Looks like a duplicate of #17722.

[edi9999]

This can be closed , since it is fixed in the 5.6.0 version :

bc263c3 #19054 Fully cross-platform package-lock.json. Installing a failing optional dependency on one platform no longer removes it from the dependency tree, meaning that package-lock.json should now be generated consistently across platforms! 🎉 (@iarna)

(Source : http://blog.npmjs.org/post/167963735925/v560-2017-11-27)