[rush-lib] Prioritise new subspace config via a new .npmrc template file #5102
Conversation
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
pedro-gomes-92
changed the title
pedro-gomes-92
changed the title
pedro-gomes-92
requested review from
iclanton,
octogonz,
apostolisms,
D4N14L and
dmichon-msft
as code owners
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.
Summary
Applies more accurate subspace configurations via
rush init-subspaceDetails
When creating a new subspace via
rush init-subspace, the rush .npmrc template might not be proper for the specific subspace. Instead it should rely on a empty .npmrc, so that the subspace can initially use the same configuration as the monorepository, i.e. common/config/rush/.npmrc.How it was tested
rush init-subspace --name testCheck the
common/config/subspaces/test/.npmrccontains an empty configuration.