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: ENOENT: no such file or directory, open .../node_modules/ignore/ignore.js #97

Closed
chrischambers opened this issue Oct 8, 2018 · 11 comments

Comments

@chrischambers
Copy link

Looks like this has been broken since kaelzhang/node-ignore@cbad90

@mantoni
Copy link
Owner

mantoni commented Oct 8, 2018

Can you explain how to produce this error?

@mantoni
Copy link
Owner

mantoni commented Oct 11, 2018

Ok, so no explanation and no further reports. Closing.

@mantoni mantoni closed this as completed Oct 11, 2018
@chrischambers
Copy link
Author

Apologies, I meant to get back to you when I could replicate this, but it seemed to be something particular to my local dev environment. Resolved, thanks.

@mantoni
Copy link
Owner

mantoni commented Oct 16, 2018

No worries. Thanks for coming back👌

@zhenyulin
Copy link

getting a similar issue when running eslint_d today, when running the bin I got the following error:

Error: ENOENT: no such file or directory, open '..../node_modules/pkg-dir/node_modules/find-up/index.js'

@mantoni
Copy link
Owner

mantoni commented Nov 15, 2018

@zhenyulin Can you verify this works with normal eslint? Can I also ask you to provide instructions on how to reproduce?

@zhenyulin
Copy link

@mantoni yes, eslint works for me, and it runs into this issue after I cp a repo locally to make a new one, and it still works in the original repo, so I suspect it might be some cache issue

@mantoni
Copy link
Owner

mantoni commented Nov 15, 2018

@zhenyulin Most probably. Can you check if eslint_d restart makes the issue disappear?

@zhenyulin
Copy link

@mantoni yes, it fixes the issue

though I'm getting the following from the command

Already running
Could not connect

which is a slightly confusing

was curious about how the cache was generated in eslint_d, is it bound to a hidden dir?

@mantoni
Copy link
Owner

mantoni commented Nov 15, 2018

@zhenyulin The cache lives in memory. Nothing is written to the file system. The message you're seeing when restarting seems weird. I guess you have an orphaned instance of eslint_d running. Please check your process list. You should always be able to stop and start without a message like this. There is a file in your home directory, ~/.eslint_d, which contains the port number and a security token. The message you're seeing indicates that the file exists, hence Already running, but the port number is not being listened on, hence Could not connect. Maybe the eslint_d daemon creashed which would explain the behaviors you're seeing.

@mantoni
Copy link
Owner

mantoni commented Nov 15, 2018

Ref #87

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

No branches or pull requests

3 participants