Ability to load plugins by path, not just name

It would be nice to install and update less devDependencies in our projects. Config authors, should have the choice to define plugins, parsers and maybe more in the future, as dependencies of their config modules. A self-contained config package is better dev experience in my opinion, than having to install and maintain a config, a parser, and a few plugin packages on every project.

One way to do this, without relying on npm flattening, is by using file paths for those dependencies, inside config modules, which is possible for parsers but not for plugins.

A “path to package name” aliasing on top, could also allow us to write eslint-disable-line plugin/rule, instead of eslint-disable-line /path/to/plugin/rule, when using file paths. Same for warning and error messages.

The goal is to be able to write npm i -D eslint eslint-config-selfcontained on a new project.

PR: #6016 Related issue: #3458 ESLint version: 2.9.0

[nzakas]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to be implemented after 90 days tend to never be implemented, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.

[muuvmuuv]

Any updates here? I’m using an extension for VSCode that is using its own eslint installation and I want eslint to load the plugin from my project.