Removing publishConfig#167
Merged
Merged
Conversation
The publishConfig specified the public npm registry. This is the default registry and is also specified in the npm publish github action, so publishConfig within the package is not necessary. Additionally, publishConfig overrides the target registry specified in any other way (.npmrc, cli, github action), making it impossible to publish to test or private registries, without manually modifying the package.
Member
|
back from the days when I used custom registries most likely. |
ctalkington
approved these changes
Feb 27, 2024
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
2 participants
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.
The publishConfig in package.json tied the package to the public npm registry. npmjs.org is the default registry and is also specified in the npmpublish.yml github action, so publishConfig within the package is not necessary. Additionally, publishConfig overrides the target registry specified in any other way (.npmrc, cli, github action), making it impossible to publish to test or private registries without manually modifying the package.