Skip to content

19.3 has a different behaviour on creating .npmrc #45881

Description

@mariovor

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:

  1. Clean container
  2. Execute a npm i in a folder not the home dir.
  3. 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.

Activity

  1. bnoordhuis commented on Dec 16, 2022

    @bnoordhuis
    Member

    You should report that to npm. Node bundles npm but we don't maintain it.

  2. added
    npmIssues and PRs related to the npm client dependency or the npm registry.
    wrong repoIssues that should be opened in another repository.
    on Dec 16, 2022
  3. mariovor commented on Dec 16, 2022

    @mariovor
    Author

    Sorry, my mistake.

  4. targos commented on Dec 16, 2022

    @targos
    Member

    @nodejs/npm FYI

  5. lukekarrys commented on Jan 2, 2023

    @lukekarrys
    Member

    This will be fixed in the upcoming npm@9.3.0 release: npm/cli#5974

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    npmIssues and PRs related to the npm client dependency or the npm registry.wrong repoIssues that should be opened in another repository.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions