Skip to content

package nicknames and dependency bumps #185

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
jbolda opened this issue Apr 8, 2021 · 1 comment
Open

package nicknames and dependency bumps #185

jbolda opened this issue Apr 8, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@jbolda
Copy link
Owner

jbolda commented Apr 8, 2021

When specifying the config.json, we can use a nickname instead of being required to use the name listed in package.json, for example. This is especially helpful for monorepos that have multiple languages, each with exact same name (which is valid since they are published to different registries). It is also nice when many of your packages have a scope (@scoped-name/package in npm).

Currently, dependencies are bumped in a package file (noting #184), but this check makes use of the package nickname. This will likely never result in a match, and leave dep/devDep without an incremented version number. When we do this search, we should use the package file name instead.

@jbolda jbolda added the bug Something isn't working label Apr 8, 2021
@jbolda
Copy link
Owner Author

jbolda commented May 5, 2022

It is possible that this is resolved and we haven't fully confirmed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant