Config is not found with scoped package
See original GitHub issueI createad a package called conventional-changelog-lint-config-<companyname>
. I would like to use it like
{
"extends": ["<companyname>"]
}
But it is a private for now and it is scoped using @<companyname>
, so to use it I have to write the full name
{
"extends": ["@<companyname>/conventional-changelog-lint-config-<companyname>"]
}
It works, but it is quite annoying. Is there an easy to fix that?
Affected packages
- cli
- core
- prompt
- config-angular
Your Environment
Executable | Version |
---|---|
commitlint --version |
7.5.2 |
git --version |
git version 2.17.2 (Apple Git-113) |
node --version |
v10.15.1 |
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Can not install npm scoped package - Stack Overflow
I setup my scope registry according to docs at https://docs.npmjs.com/misc/scope here is config list output: C:\Users\anam\Desktop\login_page> ...
Read more >[BUG] npm install picks the wrong registry when ... - GitHub
Try to find it in the public npm registry. There is no way to handle when a scope @Company, has public and private...
Read more >scope - npm Docs
Scoped packages are not public by default. You will need to specify --access public with the initial npm publish command. This will publish...
Read more >npm Registry - JFrog - JFrog Documentation
Artifactory fully supports npm scope packages. The support is transparent to the user and does not require any different usage of the npm ......
Read more >Installing private npm modules · Gemfury Dev Center
Remember to use the blended index to seamlessly mix public and private dependencies in your project. Working with scoped packages. Uploading a scoped...
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
Quick status update, we have fixed the strange behavior of one of our dependencies. But to get everything going in the right direction, we need to fix #599 before we should release a new one. That issue is also blocked by comsiconfig#180. Bare with us here 😄
Hi, thanks a lot for all the quick answers. I can rename my package to follow the new convention, no problem with that 🎉