Skip to content

Conversation

@elyobo
Copy link

@elyobo elyobo commented Oct 8, 2025

See #89.

Checks for a project local .npmrc before the user .npmrc, which avoids potentially misleading log messages (not finding a user .npmrc is not a problem if there's a project one) and unecessarily generating a user .npmrc.

@changeset-bot
Copy link

changeset-bot bot commented Oct 8, 2025

🦋 Changeset detected

Latest commit: 970e050

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@changesets/action Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@elyobo elyobo force-pushed the lo/check-project-npmrc branch from d7f98be to 5c94ce4 Compare October 8, 2025 20:37
@elyobo
Copy link
Author

elyobo commented Oct 8, 2025

@Andarist this is the sort of change I was thinking of for #89; if it's something you'd consider I can look at adding the appropriate tests (there don't seem to be any explicitly checking the .npmrc handling at the moment, but the existing tests pass).

See changesets#89.

Checks for a project local `.npmrc` before the user `.npmrc`, which
avoids potentially misleading log messages (not finding a user `.npmrc`
is not a problem if there's a project one) and unecessarily generating
a user `.npmrc`.
@elyobo elyobo force-pushed the lo/check-project-npmrc branch from 5c94ce4 to 970e050 Compare October 8, 2025 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant