-
-
Notifications
You must be signed in to change notification settings - Fork 33.6k
Closed as not planned
Labels
npmIssues and PRs related to the npm client dependency or the npm registry.Issues and PRs related to the npm client dependency or the npm registry.wrong repoIssues that should be opened in another repository.Issues that should be opened in another repository.
Description
Version
v19.3.0
Platform
Linux 8c48bb36138c 5.15.0-56-generic #62~20.04.1-Ubuntu SMP Tue Nov 22 21:24:20 UTC 2022 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
Executed in Docker:
- Clean container
- Execute a
npm iin a folder not the home dir. - Execute a
npm config set ...
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior?
In node 19.2 -> Create .npmrc in home dir (in case of container /root/.npmrc)
What do you see instead?
In node 19.3 -> Create .npmrc in directory executed the npm i
Additional information
Not sure if this is expected, but I did not find anything in the Changelog. Caught this in our CI pipeline because it operated on ~/.npmrc.
Metadata
Metadata
Assignees
Labels
npmIssues and PRs related to the npm client dependency or the npm registry.Issues and PRs related to the npm client dependency or the npm registry.wrong repoIssues that should be opened in another repository.Issues that should be opened in another repository.