npm@3.5.0 should not be trying to install modules that arch/os say are incompatible

[rstoenescu]

A reference to #8921.
Was fixed with npm 3.3.12, now it doesn't works again, with npm 3.5.0

[othiym23]

Do you have an example of how to reproduce it? We have a few test cases around this functionality that are still passing, so it seems we've overlooked something.

[rstoenescu]

Test case: install quasar-framework package on a Linux machine.

Seems like fsevents is not supported on Linux (and it shouldn't, since it's MacOS specific):

npm ERR! notsup Not compatible with your operating system or architecture: fsevents@1.0.5

[Plummat]

getting this with fsevents@1.0.5, which is also unfortunately busting our CI builds.

[rstoenescu]

Any progress on this one? For reproduction, use a VM with Linux (most likely Windows too) and try to install quasar-framework.

Thanks!

[yonatanmn]

same happens to me :
windows,
npm@3.5.2, node@4.2.2
git clone https://github.com/facebook/react-native.git
npm install

 fsevents@1.0.5 install C:\projects\react-native\node_modules\fsevents
> node-pre-gyp install --fallback-to-build

Traceback (most recent call last):
  File "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\gyp\gyp_main.py", line 16, in <module>
    sys.exit(gyp.script_main())
  File "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 545, in script_main
    return main(sys.argv[1:])
  File "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 538, in main
    return gyp_main(args)
  File "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\__init__.py", line 523, in gyp_main
    generator.GenerateOutput(flat_list, targets, data, params)
  File "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py", line 2003, in GenerateOutput
    sln_projects, project_objects, flat=msvs_version.FlatSolution())
  File "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py", line 1762, in _GatherSolutionFolders
    return _DictsToFolders('', root, flat)
  File "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\generator\msvs.py", line 1715, in _DictsToFolders
    for folder, contents in bucket.iteritems():
AttributeError: 'MSVSProject' object has no attribute 'iteritems'
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:305:16)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Windows_NT 10.0.10586
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "configure" "--fallback-to-build" "--module=C:\\projects\\react-native\\node_modules\\fsevents\\lib\\binding\\Release\\node-v46-win32-x64\\fse.node" "--module_name=fse" "--module_path=C:\\projects\\react-native\\node_modules\\fsevents\\lib\\binding\\Release\\node-v46-win32-x64"
gyp ERR! cwd C:\projects\react-native\node_modules\fsevents
gyp ERR! node -v v4.2.2
gyp ERR! node-gyp -v v3.2.1
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files\nodejs\node.exe C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=C:\projects\react-native\node_modules\fsevents\lib\binding\Release\node-v46-win32-x64\fse.node --module_name=fse --module_path=C:\projects\react-native\node_modules\fsevents\lib\binding\Release\node-v46-win32-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (C:\projects\react-native\node_modules\fsevents\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:87:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:818:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
node-pre-gyp ERR! System Windows_NT 10.0.10586
node-pre-gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\projects\\react-native\\node_modules\\fsevents\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd C:\projects\react-native\node_modules\fsevents
node-pre-gyp ERR! node -v v4.2.2
node-pre-gyp ERR! node-pre-gyp -v v0.6.15
node-pre-gyp ERR! not ok
Failed to execute 'C:\Program Files\nodejs\node.exe C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=C:\projects\react-native\node_modules\fsevents\lib\binding\Release\node-v46-win32-x64\fse.node --module_name=fse --module_path=C:\projects\react-native\node_modules\fsevents\lib\binding\Release\node-v46-win32-x64' (1)
npm WARN install:fsevents@1.0.5 fsevents@1.0.5 install: `node-pre-gyp install --fallback-to-build`
npm WARN install:fsevents@1.0.5 Exit status 1

[gemina]

same here on Ubuntu 14.04

node: v5.3.0
npm: 3.5.2

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.6

[joerideg]

Same here on Linux Mint
node: v5.3.0
npm: 3.5.2

[CrescentKohana]

Same with Debian 8.2.

41 verbose stack Error: Unsupported
41 verbose stack at checkPlatform (/usr/lib/node_modules/npm/node_modules/npm-install-checks/index.js:46:14)
41 verbose stack at Array. (/usr/lib/node_modules/npm/node_modules/slide/lib/bind-actor.js:15:8)
41 verbose stack at LOOP (/usr/lib/node_modules/npm/node_modules/slide/lib/chain.js:15:14)
41 verbose stack at /usr/lib/node_modules/npm/node_modules/slide/lib/chain.js:18:7
41 verbose stack at checkEngine (/usr/lib/node_modules/npm/node_modules/npm-install-checks/index.js:25:10)
41 verbose stack at Array. (/usr/lib/node_modules/npm/node_modules/slide/lib/bind-actor.js:15:8)
41 verbose stack at LOOP (/usr/lib/node_modules/npm/node_modules/slide/lib/chain.js:15:14)
41 verbose stack at chain (/usr/lib/node_modules/npm/node_modules/slide/lib/chain.js:20:5)
41 verbose stack at module.exports.isInstallable (/usr/lib/node_modules/npm/lib/install/validate-args.js:26:3)
41 verbose stack at Array. (/usr/lib/node_modules/npm/node_modules/slide/lib/bind-actor.js:15:8)
42 verbose pkgid fsevents@1.0.6
43 verbose cwd /home/luuq/d-zone
44 error Linux 3.16.0-4-amd64
45 error argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "fsevents"
46 error node v5.3.0
47 error npm v3.5.2
48 error code EBADPLATFORM
49 error notsup Not compatible with your operating system or architecture: fsevents@1.0.6
50 error notsup Valid OS: darwin
50 error notsup Valid Arch: any
50 error notsup Actual OS: linux
50 error notsup Actual Arch: x64

[AkessonHenrik]

Same problem for me with some packages like mysql, sqlite, sequelize, etc. on windows 10.

Not compatible with your operating system or architecture: fsevents@1.0.6

[gnomesoftuk]

Exact same issue here on Ubuntu 14.04.3 LTS
Node : 4.2.4
Npm : 3.5.2

npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.6

Rolling back to 3.3.12 seems to fix it.

I am unable to determine which dependency is causing the issue from npm's output.

[codingquark]

@gnomesoftuk I'm unable to fix it by rolling back 3.3.12

Node versions tried: 4.2.4, 5.4.1
npm versions tried: 3.3.12, 3.5.2
OS: Ubuntu 14.04 LTS

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.6

[diegoarcega]

Same

45 error Linux 4.2.0-23-generic
46 error argv "node" "/usr/local/bin/npm" "install" "fsevents"
47 error node v0.10.25
48 error npm v3.5.3
49 error code EBADPLATFORM
50 error notsup Not compatible with your operating system or architecture: fsevents@1.0.6
51 error notsup Valid OS: darwin
51 error notsup Valid Arch: any
51 error notsup Actual OS: linux
51 error notsup Actual Arch: x64
52 verbose exit [ 1, true ]

[aush]

windows 10
node: 5.3.0
npm: 3.5.2

npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.6

Get this message installing any package

[anaibol]

👍 same on Linux, npm 3.5.3

[bmulcahy]

same
windows 7
node: 5.3.0
npm: 3.5.4

npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.6

rolling back to 3.3.12 fixes it

[shercoder]

Same:
OS: Linux
Arch: x64
node: 5.1.1
npm: 3.3.12

npm ERR! notsup Not compatible with your operating system or architecture: fsevents@1.0.6

[bmulcahy]

For a test case try to install ampersand-app (where I got my error)

[safqwf]

First time there is no error, but each next time I run npm install there is an error.
If I delete the node_modules folder and install tested package again, the error doesn't show up.
Tested package is semantic-ui

[SergeyKhval]

same here. fails to install gulp-sass
OS: Windows 7
node: 4.2.6
npm: 3.5.3

[anonimusprogramus]

Same here.
OS: Arch Linux 64bit
node: 5.5.0
npm: 3.5.3

step #1 git clone https://github.com/vuejs/vue-hackernews.git
step #2 npm install

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.6

[obust]

same here
ubuntu: 15.10
node: 5.5.0
npm: 3.5.3

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.6

[javierav]

Same trying to install pm2:

• OS: Ubuntu 14.04.3 LTS
• node: v0.10.41
• npm: 3.5.3

npm WARN optional Skipping failed optional dependency /pm2/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.6

[mikemaccana]

Quick reminder to all: if you haven't seen it yet, scroll up and read: "If you get a WARN and are worried this bug affects you" above.

[franz-josef-kaiser]

@mikemaccana you should really stop sticking bold headlines into peoples faces. That never works out.

[mikemaccana]

@franz-josef-kaiser It's h1 because a lot of people are confused and I want them to see it. DBAA.

[Wildhoney]

h2s are less controversial.

[dikiaap]

Calm down. I sell orange, offer 50% discount !!

[kangarooo]

Had Chrome repo with chrome installation and with that i got nore 0.10.25. Also maybe old npm cause
student@student-Web-Frontend:~/proangular/angular$ npm install webpack
npm WARN prefer global node-deb@0.1.10 should be installed with -g
myfacebook@1.0.0 /home/student/proangular/angular
├── angular@1.5.0
├── angular-aria@1.5.0
├── angular-material@1.0.6
├── angular-messages@1.5.0 extraneous
├── bootstrap@3.3.6
├── node-deb@0.1.10 extraneous
└── webpack-dev-server@1.14.1

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.8
npm WARN myfacebook@1.0.0 No description

student@student-Web-Frontend:~/proangular/angular$ npm install fsevents
npm ERR! Linux 4.2.0-30-generic
npm ERR! argv "/usr/bin/nodejs" "/home/student/.npm-global/bin/npm" "install" "fsevents"
npm ERR! node v5.7.1
npm ERR! npm v3.8.0
npm ERR! code EBADPLATFORM

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

npm ERR! Please include the following file with any support request:
npm ERR! /home/student/proangular/angular/npm-debug.log

I have UBUNTU 15.10

[freddy24]

@yonatanmn have you solved this problem?I got the same problem as you

[thilinamgit]

Same kind of issues occurring on,
Node: v0.10.42
NPM: 3.7.3

---

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.8
Updating Angular UI Bootstrap Components
npm WARN angular-ui-bootstrap@0.12.0 No repository field.

---

[MichelBakker]

Same here:

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.8
npm ERR! Linux 3.19.0-25-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v5.7.0
npm ERR! npm v3.8.2
npm ERR! path ../acorn/bin/acorn
npm ERR! code EPROTO
npm ERR! errno -71
npm ERR! syscall symlink

npm ERR! EPROTO: protocol error, symlink '../acorn/bin/acorn' -> '/home/vagrant/~/node_modules/.bin/acorn'

[WhatFreshHellIsThis]

Why does it show any message at all on a non OSX OS if it's completely irrelevant to a non OSX user? This just seems like something that should go away.

[kimtn-bitmark]

@kangarooo did you resolve your problem. The same here

npm ERR! argv "/home/vagrant/.nvm/versions/node/v5.8.0/bin/node" "/home/vagrant/.nvm/versions/node/v5.8.0/bin/npm" "install" "fsevents"
npm ERR! node v5.8.0
npm ERR! npm  v3.7.3
npm ERR! code EBADPLATFORM

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

ubuntu 15.10

[mikemaccana]

@franz-josef-kaiser See why now? 50% of folk here haven't read the thread. Anyway I'm out unsubscribes.

[franz-josef-kaiser]

@mikemaccana well, that one we agree. unsubscribe

[WhatFreshHellIsThis]

@mikemaccana are you criticizing people for reporting this error that really should not be shown to the user in the first place? What difference does it make if it's not a real problem and just cosmetic? It's still an issue and it's still not resolved and that's a bit mystifying but reports will continue until it is.

[WhatFreshHellIsThis]

Surely the "needs repro" label can be removed now?

[joshmanders]

@mikemaccana That doesn't fix it for everyone. npm uses the npmlog module for logging warnings and errors, the module by DEFAULT logs to stderr which in MY case, causes things that check for messages on stderr and errors out, such as Docker is a problem. Your "cosmetic" solution isn't a one size fits all. So stop saying the problem is fixed when it clearly isn't.

[GitMiester]

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.8
npm ERR! Linux 3.13.0-79-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.4.0
npm ERR! npm v3.8.1
npm ERR! code ELIFECYCLE

[mikemaccana]

@WhatFreshHellIsThis

are you criticizing people for reporting this error that really should not be shown to the user in the first place?

No. There is no reason anyone would think that.

What difference does it make if it's not a real problem and just cosmetic?

Because they're separate behaviours, with separate causes - ERR stops installation completely, WARN is just a warning - and the WARN is (and should be) a separate bug, #11632

[WhatFreshHellIsThis]

@mikemaccana I think you need to re-read the initial reported case in this bug here and you need to consider retracting bug #11632 because it makes no sense to report anything to anyone when it doesn't apply to their operating system. This case already has a proper request and will fix the problem in a correct manner. Reporting completely irrelevant information is still reporting completely irrelevant information, it's better that install doesn't fail yes, but any seasoned developer knows you don't show irrelevant confusing information to users, it's a recipe for more bug reports and more hassle all around.

[burzum]

This happens as well for me with NodeJS 5.8.0, Npm 3.7.3 on 14.04.1-Ubuntu.

[Cardoso222]

Same here, NodeJS 5.8.0, NPM 3.7.3 on 14.04 ubuntu.

[kfrost89]

Same issue on Arch Linux. NodeJS 5.9.0 and NPM 3.8.1

[mikemaccana]

@WhatFreshHellIsThis you just said

it makes no sense to report anything to anyone when it doesn't apply to their operating system

Reducing the severity of the warning exactly what #11632 is there to fix - you might prefer nothing at all to INFO but some people would like to know why something's being skipped. However if you have something to say, make it in that bug.

This bug is for npm trying to install modules that arch/os say are incompatible, which you can tell from the title. Since this conversation isn't really helping anyone I've blocked you.

[WhatFreshHellIsThis]

@mikemaccana I stand by what I said, if you don't want to hear it or think about it that's your call.

[othiym23]

There are 83 comments on this issue now, and I think it long ago passed the point of diminishing returns. The actionable piece of this is preserved in #11632, and if there are other pieces of this that users would like to see addressed, please file new issues. Thanks to all for their time!