How should ESLint dependencies be handled?

I’m currently working on adding ESLint support thanks to https://github.com/Quramy/typescript-eslint-language-service.

However, I don’t have much experience using ESLint and it’s expected workflow.

Should users be expected to have ESLint (+ it’s dependencies) installed in the node_modules folder of the project they are working on?

Or are they expecting ESLint (+ dependencies) to be installed already when they install Wild Web Developer?

The issue with the second workflow is that ESLint looks for it’s dependencies relative to the location of it’s configuration file .eslintrc (which are configured on a per-project-basis), so the user would have to specify the path to the Wild Web Developer bundle location in this configuration. This would also probably cause some issues with Eclipse running in Flatpak.

[Christopher-Chianelli]

Typically (in my experience), eslint is installed in node_modules for each project that use it. +1 to the first approach (users be expected to have ESLint (+ it’s dependencies) installed in the node_modules folder of the project they are working on).

[jabby]

@AObuchow same experience for me. All projects with eslint have the eslint in node_modules.

About extention. If we don’t have any projetcs in workspace with corresponding dependency (eslint here and angular for #276) maybe we should not load the plugin.