-
-
Notifications
You must be signed in to change notification settings - Fork 298
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
Allow publishConfig.registry
to be npm default registry
#749
Comments
// @mifi |
fisker
changed the title
It's allow
Allow Jun 29, 2024
publishConfig.registry
to be npm default registrypublishConfig.registry
to be npm default registry
Yeah I didn't implement support for that when I added berry support. Feel free to submit a PR if there's an easy way to add support for it. |
This was referenced Jul 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I have
in all my packages. When using yarn berry, np throws a error,
Steps to reproduce
yarn set version berry
np
Expected behavior
Not throw errors.
Environment
np - 10.0.6
Node.js - 22
npm - Should not releated
Git - Should not releated
OS - Should not releated
Related code
np/source/npm/util.js
Line 46 in a9e8fc7
The text was updated successfully, but these errors were encountered: