-
Notifications
You must be signed in to change notification settings - Fork 10
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
Allow running ESLint using npx #26
Comments
thanks for raising an issue. until I get some time to work on this again (and it needs a lot of work!), would updating the buffer-local value of (push
(file-name-concat
(locate-dominating-file
(buffer-file-name)
"package.json")
"node_modules" ".bin")
exec-path)
(flymake-eslint-enable) that should first try |
Thanks for your reply! That sounds like a workable solution, thanks for the tip! 👍 |
codesuki/add-node-modules-path might help. |
found this code snippet: (use-package flymake-eslint
:custom
(flymake-eslint-executable-name "npx")) |
Currently, ESLint needs to be in
executable-path
, which means that ESLint must be installed globally orexecutable-path
has to be configured per project. It would be nice ifflymake-eslint
would offer the possibility to run ESLint through NPM's npx command instead (npx eslint
), which would automatically pick up the ESLint version installed in the project'snode_modules
, and only runs the globally installed version as a fallback.The text was updated successfully, but these errors were encountered: