#4 Rely on user .npmrc instead of project .npmrc#5
Merged
normanlolx merged 1 commit intomainfrom Feb 4, 2026
Merged
Conversation
normanlolx
changed the title
normanlolx
force-pushed
the
3-global-npmrc
branch
from
67a556c to
096f493
Compare
Collaborator
|
I like to keep as much "local to the project" as possible (so things don't bleed across projects) - but am very open to hear your arguments :) Should we keep the "local ..npmrc" as an option? |
Member
Author
You can still have a local .npmrc, but the token does definitely not need to be put there. |
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.
Let's use the user's .npmrc
And let's also check if it contains a glpat- entry
Closes #4