Skip to content

[BUG] npm_command env not getting set #2015

Description

@isaacs

At some point in the v7 beta/rc line, we shuffled around the order of when configs are loading and envs are set, and ended up clobbering the npm_command environment variable.

Current Behavior:

{
  "name": "test-command-env",
  "version": "1.0.0",
  "scripts": {
    "test": "echo $npm_command"
  }
}
$ npm test

> test-command-env@1.0.0 test
> echo $npm_command

null

Expected Behavior:

$ npm test

> test-command-env@1.0.0 test
> echo $npm_command

test

Activity

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

    Bugthing that needs fixingNeeds Triageneeds review for next stepsRelease 7.xwork is associated with a specific npm 7 release

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions