-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Ability to load plugins by path, not just name #6237
Copy link
Copy link
Closed
Labels
acceptedThere is consensus among the team that this change meets the criteria for inclusionThere is consensus among the team that this change meets the criteria for inclusionarchived due to ageThis issue has been archived; please open a new issue for any further discussionThis issue has been archived; please open a new issue for any further discussionblockedThis change can't be completed until another issue is resolvedThis change can't be completed until another issue is resolvedcoreRelates to ESLint's core APIs and featuresRelates to ESLint's core APIs and featuresenhancementThis change enhances an existing feature of ESLintThis change enhances an existing feature of ESLinthelp wantedThe team would welcome a contribution from the community for this issueThe team would welcome a contribution from the community for this issueneeds bikesheddingMinor details about this change need to be discussedMinor details about this change need to be discussed
Description
Activity
Metadata
Metadata
Assignees
Labels
acceptedThere is consensus among the team that this change meets the criteria for inclusionThere is consensus among the team that this change meets the criteria for inclusionarchived due to ageThis issue has been archived; please open a new issue for any further discussionThis issue has been archived; please open a new issue for any further discussionblockedThis change can't be completed until another issue is resolvedThis change can't be completed until another issue is resolvedcoreRelates to ESLint's core APIs and featuresRelates to ESLint's core APIs and featuresenhancementThis change enhances an existing feature of ESLintThis change enhances an existing feature of ESLinthelp wantedThe team would welcome a contribution from the community for this issueThe team would welcome a contribution from the community for this issueneeds bikesheddingMinor details about this change need to be discussedMinor details about this change need to be discussed
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 ofeslint-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-selfcontainedon a new project.PR: #6016
Related issue: #3458
ESLint version: 2.9.0