fix: use npm as package manager for nx release publish#1098
Merged
Conversation
Set cli.packageManager to npm in nx.json so nx release publish uses npm rather than yarn for publishing. Restore registry-url in setup-node so npm has the registry configured for auth. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 09e61ec:
|
Use release.publish.targetDefaults.args in nx.json to pass --package-manager=npm and --provenance to the publish target instead of overriding the global cli.packageManager. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Set cli.packageManager to npm in nx.json so nx release publish uses npm rather than yarn for publishing. Restore registry-url in setup-node so npm has the registry configured for auth.