You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
When specifying the
config.json
, we can use a nickname instead of being required to use the name listed inpackage.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.
The text was updated successfully, but these errors were encountered: