Change Request: Eslint plugins exported via custom entry-point

[danieldelcore]

ESLint version

v7.7.0

What problem do you want to solve?

Support the ability to register eslint plugins exposed via custom entry-points.

For example, a package which contains source code for the package itself and all supporting tooling related to the package, including an eslint plugin.

Currently the docs state:

Each plugin is an npm module with a name in the format of eslint-plugin-, such as eslint-plugin-jquery. You can also use scoped packages in the format of @/eslint-plugin- such as @jquery/eslint-plugin-jquery or even @/eslint-plugin such as @jquery/eslint-plugin.

But to support this use case we would need eslint to support the following: @scope/packageName/eslint-plugin-packageName

What do you think is the correct solution?

Eslint could be updated to be entry-point aware when attempting to register plugins.

Potentially by updating this logic (maybe 😬):

eslint/lib/init/config-initializer.js

Line 115 in a744dfa

const moduleName = naming.normalizePackageName(plugin, "eslint-plugin");

Participation

• I am willing to submit a pull request for this change.

Additional comments

No response

[nzakas]

We aren’t making any changes to how plugins work in the current config system. The new config system doesn’t have any constraints on how your plugins are packaged.