Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fsevent keeps failing under Arch Linux #21642

Closed
Jzarecta opened this issue Jul 3, 2018 · 3 comments
Closed

fsevent keeps failing under Arch Linux #21642

Jzarecta opened this issue Jul 3, 2018 · 3 comments
Labels
npm Issues and PRs related to the npm client dependency or the npm registry. question Issues that look for answers. wrong repo Issues that should be opened in another repository.

Comments

@Jzarecta
Copy link

Jzarecta commented Jul 3, 2018

  • 10.5:
  • GNU/Linux Arch:
  • x64:

Keep finding issues with fserve trying to guess my OS

``
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 672 packages from 769 contributors and audited 4055 packages in 31.316s
found 11 low severity vulnerabilities
run npm audit fix to fix them, or npm audit for details
``

@addaleax
Copy link
Member

addaleax commented Jul 3, 2018

What’s the expected behaviour, what is the actual behaviour? Which library did you originally want to install?

I think this might be better kept for the help repo at https://github.com/nodejs/help/. It seems like this is either an issue with fsevents or with npm, not with Node.js. Without more information, it’s most likely that it’s just a warning that you can just ignore.

@addaleax addaleax added question Issues that look for answers. npm Issues and PRs related to the npm client dependency or the npm registry. labels Jul 3, 2018
@Jzarecta
Copy link
Author

Jzarecta commented Jul 3, 2018

I expect to detect my Linux system without a warning flag.

@ChALkeR ChALkeR added the wrong repo Issues that should be opened in another repository. label Jul 3, 2018
@ChALkeR
Copy link
Member

ChALkeR commented Jul 3, 2018

This should be reported to either fsevents, npm, or the library using fsevents, or nodejs/help repo.
This warning is not coming from or caused by Node.js.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
npm Issues and PRs related to the npm client dependency or the npm registry. question Issues that look for answers. wrong repo Issues that should be opened in another repository.
Projects
None yet
Development

No branches or pull requests

4 participants