[QUESTION] How to properly get rid of npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents

[OnkelTem]

Hi all.

I found several topics discussing how to get rid of messages like these:

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/webpack-dev-server/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/watchpack/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/jest-haste-map/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

and it seems like npm i -f is gonna "fix" this issue, but unfortunately what has never been explained is what exactly it's doing and how it's working.

Another advice was to run npm i with parameter --no-optional.
Well, first - I'm not gonna skip other optionals as well just because npm complains about this one (which one cannot even install on Linux).
And second - it's not convenient to run npm with additional --no-optional parameter every time, eh?

So my question is: how to get rid of this specific warning about "fsevents" which is not supposed to be installed on Linux? Is there a way to add some "rule" or something into package.json to not warn on standard OSes like Linux and keep it showing on proprietary ones?

[jakerobb]

Hey @jacksonrayhamilton, it's been just about two years since you said you'd do this in a year or two. How about resubmitting that PR? 🙂

[jacksonrayhamilton]

😆 I was being sarcastic.

Someone else already resubmitted it here: #169

I stumbled on this blog post recently which alludes to the problem being fixed in v7: https://blog.npmjs.org/post/617484925547986944/npm-v7-series-introduction

Coming Attractions
In the coming npm v7 posts, we’ll cover:

• Fixing the “noisy chokidar/fsevents” problem

Hopefully someone from the NPM org will stop by some of these open issues and confirm that explicitly.

[jakerobb]

😆 I was being sarcastic.

Oh, I know. I was mostly trolling the project organizers for the ridiculousness that was this thread and the fact that this is still an issue. 🙃

Someone else already resubmitted it here: #169

I stumbled on this blog post recently which alludes to the problem being fixed in v7: https://blog.npmjs.org/post/617484925547986944/npm-v7-series-introduction

Coming Attractions
In the coming npm v7 posts, we’ll cover:

• Fixing the “noisy chokidar/fsevents” problem

Hopefully someone from the NPM org will stop by some of these open issues and confirm that explicitly.

Awesome!

[jacksonrayhamilton]

#169 (comment)

Yep, it’s fixed in v7.

[darcyclarke]

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.