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

Error installing fsevents dependency #95

Closed
brianchirls opened this issue Aug 31, 2018 · 3 comments · Fixed by #97
Closed

Error installing fsevents dependency #95

brianchirls opened this issue Aug 31, 2018 · 3 comments · Fixed by #97
Assignees
Labels

Comments

@brianchirls
Copy link

This package includes an old version of fsevents as an optional dependency. I'm unable to install that package on my version of OSX with the latest Node engine. It's not absolutely necessary, but it does screw things up. The issue I reference seems to be fixed with newer versions of fsevents. But it's an exact version match, so it won't upgrade automatically.

I can't figure out why this dependency is in here, since I don't see it referenced in any other code, unless it's vestigial and not really necessary.

Please upgrade the dependency version or remove it. Thank you.

@hoch hoch added the bug label Sep 4, 2018
@hoch
Copy link
Member

hoch commented Sep 4, 2018

I think it is a part of dependency chain of ESlint, which is required by GoogleChrome org. I will try to update the package info, but could you let me know your version of Node engine and OSX?

@brianchirls
Copy link
Author

I'm running node v10.9.0 and OSX 10.13.6

I don't see it anywhere in the eslint dependency chain. It is in the chain for webpack, but I believe it should be a newer version.

Thanks.

@hoch hoch self-assigned this Sep 5, 2018
@hoch
Copy link
Member

hoch commented Sep 5, 2018

Thanks for looking into it. I will have some time to tackle it in this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants