[BUG] replacement for npm_config_argv in v8.5.0
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
When trying to use npm_config_argv, it appears to be removed. I am wondering what is the replacement for npm_config_argv, i tried to search around, and it says "Where the argv is being parsed in order to determine the command being run, the npm_command environ provides a safer approach." However, the npm_command currently holds a value of exec, does it mean this is not yet implemented?
Expected Behavior
No response
Steps To Reproduce
console.log(process.env.npm_config_argv)
process.env.npm_config_argv is undefined
Environment
- npm:
8.5.0 - Node.js:
v16.14.2 - OS Name:
MacOS 10.15.7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported process.env.npm_config_argv and npm_command values with npm 8.5.0, then trace where these environment variables are handled. Determine and document the supported replacement for npm_config_argv, and verify the resulting command information against the issue's expected use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100