Add support of local plugins

[roadhump]

eslint_d does not resolve local plugins in project's node_modules as eslint does

It means

npm install eslint eslint_d babel-eslint --save-dev

// .eslintrc
{"parser": "babel-eslint"}

$ ./node_modules/.bin/eslint_d src/1.js 

/Users/roadhump/Projects/xx/src/1.js
  0:0  error  Cannot find module 'babel-eslint'

$ ./node_modules/.bin/eslint_d src/1.js 
// no errors

[mantoni]

I guess I know why this happens: eslint uses a simple require statement to load the configured parser. If the eslint_d server was started in a directory that doesn't have the parser in the node_modules resolve path, it can't find the parser. You can easily check by running eslint_d restart, which should fix it.

A possible solution could be to run a new eslint_d server for each directory in use, or restart the existing one transparently whenever the directory changes. Any other ideas?

[Schniz]

Maybe: whenever I call to eslint_d, it adds the current directory to the module resolver, and removes it afterwards?

[Schniz]

Or synlinking and unlinking afterwards

[mantoni]

Just release eslint_d v2.2.0 which addresses this issue. See the changelog entry for details.

@roadhump @Schniz Can you please test whether this works for you now? I'd appreciate your feedback, or new issues in case things don't work as expected.

[roadhump]

@mantoni seems working just fine, thank you!

[Schniz]

@mantoni works great! 👍

[expelledboy]

@mantoni Amazing work! I have just noticed that if I change the plugin configuration in .eslintrc after using eslint_d that it requires a eslint_d restart. Would be useful if it was auto-restarted on changes to that file, or just add a note to the README.

[mantoni]

Yes, this could be added to the readme…