-
Notifications
You must be signed in to change notification settings - Fork 922
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Current state of @commitlint/config-lerna-scopes #4262
Comments
Hey @janbiasi , thanks for opening this up and your write up and proposal! ❤ The current lerna state isn't intended and kinda unwanted. We got stuck here because I'm lacking time and motivation to update commitlint itself to a new/updated monorepo setup. I'm more than happy if you want to try out your proposal. |
Hey @escapedcat 👋🏽 thanks for your fast response! I'll start with my work today and keep this issue updated regarding my progress. Below are links to the PRs as soon as they're drafted:
|
Update: I'm currently blocked by lerna not allowing to specify a custom @escapedcat The PR for the workspace scopes is already ready for review. |
Hey!
Currently, the @commitlint/config-lerna-scopes depends on the deprecated @lerna/project which is not maintained, nor does it exist anymore. I'd be willing to contribute to the package to make the deprecated dependency an optional peer dependency, however a few thoughts crossed my mind which I'd want to discuss before investing time;
config-workspace-scopes
into a separate package - with no dependencies - for the users who only need support forworkspaces
inpackage.json
?package.json
workspaces
field, so most of the users transitioned to themnx
and I wasn't able to find a reliable way in each version on how to retrieve them safelynx
because of the state of the project.My summary as well as proposal would be:
config-workspace-scopes
for those who are only using yarn or npm workspaces with the existing logic part from the lerna config@lerna/project
and use their "new" API to retrieve the packagesI'm looking forward to your feedback and thoughts on this topic!
*edited to fix misspelled words
The text was updated successfully, but these errors were encountered: