Commitlint: Config is not found with scoped package

[thomasthiebaud]

I 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
• [x] 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 |

[byCedric]

We _can_ adopt the ESLint method for scoped packages. I think that would suit your needs right? Also looking at @escapedcat 😉

If we are going for that one, you can use it as @<companyname>. The package should be named something like @<companyname>/commitlint-config.

[byCedric]

Created a PR with the change for scoped short notations! 🎉 Hope you like it.

Btw, I noticed that you are using a legacy naming convention for the package. It was changed from conventional-changelog-lint-config to commitlint-config. Please note that _if_ this PR with the feature is merged, your legacy-named package will not work with the short scope notation.

[thomasthiebaud]

Hi, thanks a lot for all the quick answers. I can rename my package to follow the new convention, no problem with that 🎉

[byCedric]

No worries, happy to help 😄 We'll try to get a version out asap, but we need to fix some weird behavior with some dependencies first.

[byCedric]

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 😄