Skip to content
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

[rush-lib] Prioritise new subspace config via a new .npmrc template file #5102

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

pedro-gomes-92
Copy link
Contributor

@pedro-gomes-92 pedro-gomes-92 commented Feb 11, 2025

Summary

Applies more accurate subspace configurations via rush init-subspace

Details

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

Check the common/config/subspaces/test/.npmrc contains an empty configuration.

@pedro-gomes-92 pedro-gomes-92 changed the title [rush-lib] Prioritise new subspace config via rush repository config [rush-lib] Prioritise new subspace config via a new .npmrc template fiel Feb 20, 2025
@pedro-gomes-92 pedro-gomes-92 changed the title [rush-lib] Prioritise new subspace config via a new .npmrc template fiel [rush-lib] Prioritise new subspace config via a new .npmrc template file Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs triage
Development

Successfully merging this pull request may close these issues.

1 participant