Feature request: sharable config as a scoped package
See original GitHub issueFor example, when I (@shinnn
) publish a sharable config eslint-config-myconfig
as a scoped package, npm will place it on node_modules/@shinnn/eslint-config-myconfig
after installing.
So, if I want to use the config via extends
option, I should write .eslintrc
like below:
{
"extends": "./node_modules/@shinnn/eslint-config-myconfig/index.js"
}
I’d like to use a scoped sharable config more simply, just like:
{
"extends": "@shinnn/myconfig"
}
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Shareable Configs - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >scope - npm Docs
Scopes can be associated with a separate registry. This allows you to seamlessly use a mix of packages from the primary npm registry...
Read more >Scoped registries - Unity - Manual
Scoped registries allow Unity to communicate the location of any custom package registry server to the Package Manager so that the user has...
Read more >Setup for scoped registries (private registries) - Unity Forum
Why "scoped" registries? It's to ensure determinism when deciding from which registry a package should be fetched. By using scopes, a package ......
Read more >npm packages in the Package Registry - GitLab Docs
If you plan to install a package through the instance level, then you must name your package with a scope. Scoped packages begin...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue was apparently fixed in v0.21.2, so it should already be working in 3.x.
If it’s not, can you please create a new issue?
I went with a solution that still requires the eslint-config- in the package name. If you are interested in allowing arbitrary package names, I’d be happy to take a look at implementing that, just let me know.