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

Method for Running ESLint with NPM Module Presets #76

Open
atomdmac opened this issue Sep 25, 2020 · 2 comments
Open

Method for Running ESLint with NPM Module Presets #76

atomdmac opened this issue Sep 25, 2020 · 2 comments
Labels
wontfix This will not be worked on

Comments

@atomdmac
Copy link

When developing Node.js apps, it's pretty common for a project to use NPM packages to define presets for linting settings. When a project is "docker-ized", the npm_modules directory is often installed to a Docker volume rather than within the host system. This has the drawback of making the presets unavailable to the host machine that Vim is running on.

I saw that ALE offers a g:ale_command_wrapper setting which can allow you to write a script that will run the linter within Docker. An example can be found here. The example is for a Python linter but the same approach works for Node projects when using ALE.

Is there a way to do this with coc-eslint?

@chemzqm
Copy link
Member

chemzqm commented Sep 26, 2020

No, coc-eslint use eslint module, but ale use eslint from command line.

@chemzqm
Copy link
Member

chemzqm commented Sep 26, 2020

You can configure eslint.nodePath as folder of your eslint.

@chemzqm chemzqm added the wontfix This will not be worked on label Jan 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants