[BUG] Installing local package with npm v7 in Windows partially modify package-lock with backslashes
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
Current Behavior
When installing a local dependency in Windows, the posix paths under "package-lock.dependencies" are converted to Windows style paths, with double backslashes. The paths in "package.json" and under "package-lock.packages" are kept unix style.
Expected Behavior
package-lock is kept as is when installing dependencies.
Steps To Reproduce
Clone and follow the instructions on sample repository.
Environment
- OS: Windows 10 20h2
- Node: 16.2.0
- npm: 7.13.0
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
Clone the linked sample repository and follow its reproduction steps on Windows with the stated Node and npm versions. Compare package-lock.dependencies with package.json and package-lock.packages; done means installing the local dependency no longer changes POSIX paths to doubled backslashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100