79

I'm using Ubuntu 15.04. While running the following command:

npm install fsevents

I'm getting following error:

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.11
npm WARN tutorial@1.0.0 No repository field.

Has anybody solved this?

mruanova
  • 6,351
  • 6
  • 37
  • 55
randomuser
  • 1,201
  • 2
  • 10
  • 19

7 Answers7

118

I was facing the same issue with this dependecy when building other application.

Just for the sake of knowledge and to people who are not well used to NPM, and thus uncertain about how their applications will behave:

Since fsevents is an API in OS X allows applications to register for notifications of changes to a given directory tree. Running:

npm install --no-optional

Will do the trick, with no drawbacks.

Cezar Augusto
  • 8,794
  • 5
  • 31
  • 36
  • 2
    There is the caution that this will hide all optional dependency failures. May not be a big deal as the dependencies are optional, but the ones that would work on your platform will also not be reported if they failed to install for some reason. – Steven Scott Dec 12 '16 at 21:07
  • I too faced the same problem but --no-optional didn't solved the problem. I downgraded npm version to 3.10.7 then it worked fine. – K. Siva Prasad Reddy Dec 13 '16 at 04:28
  • 1
    The first installer I've saw in my life that can't do a simple OS check. – Leo Jan 14 '17 at 14:23
  • `no-optional` didn't work for me, but upgrading node did the trick (to version 6.11.4 on Windows, not sure what version I had before) – fredw Oct 19 '17 at 18:28
11

It's not an error, it's just a warning: it's an optional dependency.

JMM
  • 26,019
  • 3
  • 50
  • 55
  • it worked without this library as well. but any way to install this library? – randomuser Apr 19 '16 at 18:23
  • 1
    I don't know if there's any way to install it (my guess would be no), but even if you could install it I don't know what that would accomplish since it's a wrapper for a native OS X API. – JMM Apr 19 '16 at 19:08
  • There were no errors! But I started searching assuming there were errors! Thanks for my eye opening!! – Mohammed H Apr 25 '18 at 05:19
10

You can tell npm not to install optional dependencies by default using the command line below:

npm config set optional false
Simon D
  • 4,150
  • 5
  • 39
  • 47
3

If you're getting ERR! not WARN a likely cause of this issue is that you're using a really outdated version of NPM

For me, I shelled into some server, and was like "why won't this work?", getting this error:

npm ERR! Linux 4.4.0-130-generic
npm ERR! argv "/home/william/.nvm/versions/node/v4.4.3/bin/node" "/home/william/.nvm/versions/node/v4.4.3/bin/npm" "install"
npm ERR! node v4.4.3
npm ERR! npm  v2.15.1
npm ERR! code EBADPLATFORM

npm ERR! notsup Unsupported
npm ERR! notsup Not compatible with your operating system or architecture: fsevents@1.1.3
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/william/app/mcard-api/npm-debug.log

Turns out this server (that I only recently acquired) was running npm 2.15.1. I re-installed nvm, and nvm install --lts fixed it.

Community
  • 1
  • 1
csga5000
  • 4,062
  • 4
  • 39
  • 52
1

I had same issue with dependency. Kindly check for the package.json file , add "typings":"^0.8.1" entry under devDependency section. dont forget to add comma before :) Hope it will resolve issue.

1

I was also facing this error when installing Redux:

$ npm install --save react-redux
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14

What solved the issue was to add --no-optional (argument will prevent optional dependencies from being installed):

npm install --no-optional --save react-redux
            ^^^^^^^^^^^^^

And now it is correctly installed:

$ npm ls redux
ReduxProject@ /home/me/projects/reduxproject
└── redux@3.5.2 
fedorqui
  • 275,237
  • 103
  • 548
  • 598
1

I found if you use "yarn add ." Yarn will exclude the fsevents will not throw an error.