Skip to content

[config-lerna-scopes] do not remove npm scope #3421

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

Open
RS-Sautter opened this issue Nov 8, 2022 · 2 comments
Open

[config-lerna-scopes] do not remove npm scope #3421

RS-Sautter opened this issue Nov 8, 2022 · 2 comments

Comments

@RS-Sautter
Copy link

RS-Sautter commented Nov 8, 2022

.map((name) => (name.charAt(0) === '@' ? name.split('/')[1] : name));

why are we removing the npm scope of the packages here?

I have the following scenario:

  • @scopeA/package1
  • @scopeB/package1

I want to be able to differentiate the two in the scopes of the commit messages, so I need to be able to write: "feat(@scopeA/package1): something new".

@escapedcat
Copy link
Member

escapedcat commented Nov 8, 2022

Looks like this was doen a long time ago?
Can't really help here. You have time and motivation to dig into this?

@RS-Sautter
Copy link
Author

@escapedcat maybe. We need to solve the referenced issue first I think, because scope-enum would not even be able to handle scoped package names atm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants