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

Intermittent issues with eslint_d #39

Closed
tribou opened this issue Apr 24, 2016 · 2 comments
Closed

Intermittent issues with eslint_d #39

tribou opened this issue Apr 24, 2016 · 2 comments

Comments

@tribou
Copy link

tribou commented Apr 24, 2016

I've been having some intermittent issues with eslint_d, and I had a couple questions.

  • Does eslint_d resolve local project eslint-config modules automatically?

I didn't know if eslint_d needed to be supplemented with a config similar to mtscout6/syntastic-local-eslint.vim to ensure it always resolves the local project config modules.

  • What's the best way to debug eslint_d?

I'm encountering intermittent issues where I have to run eslint_d restart in order to get eslint_d to work again with Syntastic. After enabling g:syntastic_debug and determining the eslint_d command being used, I found there were errors similar to this:

eslint_d -f compact src/config/env.js
Error: standard:
    Configuration for rule "no-labels" is invalid:
    Value "2,[object Object]" has more items than allowed.

Referenced from: tribou
Referenced from: /Users/tribou/dev/project/.eslintrc

The error is from the eslint-config-standard module, but it's associated with using eslint v1.x, so I'm not sure what to do with that. However, after running eslint_d restart in the project directory, the issue appears to resolve itself. Any ideas?

v2.8.0 (eslint_d v3.1.0)

@mantoni
Copy link
Owner

mantoni commented Apr 26, 2016

Hm, I would guess that eslint_d loaded an older version - e.g. from your node_modules directory. If eslint was updated to a newer version afterwards, you need to restart eslint_d to discard the old instance and load the new version.

To your questions:

Does eslint_d resolve local project eslint-config modules automatically?

It leaves the config resolution to eslint. It should work just like eslint, otherwise there's a bug (see #21)

What's the best way to debug eslint_d?

Enabling g:syntastic_debug is a very good idea. Other than that, there is clearly some more advanced error handling needed in eslint_d. It does not forward any error output from the background process.

@mantoni
Copy link
Owner

mantoni commented Jun 8, 2016

As it's not clear what the issue actually is, please update to latest eslint_d and report back if it's still not working as expected. I'm happy to reopen.

@mantoni mantoni closed this as completed Jun 8, 2016
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

2 participants