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
My suggestion is to add flag, if it's provided, script deletes private field to be able to publish the package and set the value of "publishConfig":{"registry":""} to value from flag.
What do you think about that?
The text was updated successfully, but these errors were encountered:
I'm using clean publish to upload project dependencies to corporate npm registry, that doesn't support mirroring.
Some packages contains fields to prevent publishing or allow publish to specific registries: https://docs.npmjs.com/cli/v10/using-npm/registry#how-can-i-prevent-my-package-from-being-published-in-the-official-registry
In that case I'm not able to publish it, until I manually change or delete these fields.
My suggestion is to add flag, if it's provided, script deletes
private
field to be able to publish the package and set the value of"publishConfig":{"registry":""}
to value from flag.What do you think about that?
The text was updated successfully, but these errors were encountered: