Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] Installing local package with npm v7 in Windows partially modify package-lock with backslashes #3291

Open
1 task done
guilhermetod opened this issue May 22, 2021 · 9 comments
Open
1 task done

[BUG] Installing local package with npm v7 in Windows partially modify package-lock with backslashes #3291

guilhermetod opened this issue May 22, 2021 · 9 comments
Labels
Bug thing that needs fixing config: lockfile platform:windows is Windows-specific Priority 2 secondary priority issue Release 7.x work is associated with a specific npm 7 release Release 8.x work is associated with a specific npm 8 release Release 9.x work is associated with a specific npm 9 release

Comments

@guilhermetod
Copy link

guilhermetod commented May 22, 2021 •
edited
Loading

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
@guilhermetod guilhermetod added Bug thing that needs fixing Needs Triage needs review for next steps Release 7.x work is associated with a specific npm 7 release labels May 22, 2021
@nzacca
Copy link

nzacca commented Dec 30, 2021

This is also present for version 8.3.0.

@ljharb ljharb added the Release 8.x work is associated with a specific npm 8 release label Dec 30, 2021
@ruyadorno ruyadorno added config: lockfile Priority 2 secondary priority issue platform:windows is Windows-specific and removed Needs Triage needs review for next steps labels Mar 2, 2022
@wraithgar wraithgar mentioned this issue Mar 17, 2022
Closed
2 tasks
@anurag-roy
Copy link

+1, commenting for visibility!

@souravsaraf123
Copy link

+1 waiting for this to be solved :)

@httpete
Copy link

httpete commented Apr 15, 2022

This is hitting us as well. It is a pretty lame bug. This effectively blocks cross platform development when using a file:/path locally installable package.

@anurag-roy
Copy link

Any update on this?

@souravsaraf123
Copy link

3 months , any update please ?

@souravsaraf123
Copy link

souravsaraf123 commented Aug 10, 2022 •
edited
Loading

please prioritize this 😞

@souravsaraf123
Copy link

any updates on this ?

@ljharb ljharb added the Release 9.x work is associated with a specific npm 9 release label Feb 15, 2023
@donaldkg
Copy link

donaldkg commented Jun 1, 2023

it has been a while. Any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug thing that needs fixing config: lockfile platform:windows is Windows-specific Priority 2 secondary priority issue Release 7.x work is associated with a specific npm 7 release Release 8.x work is associated with a specific npm 8 release Release 9.x work is associated with a specific npm 9 release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@ljharb @ruyadorno @nzacca @httpete @donaldkg @souravsaraf123 @guilhermetod @anurag-roy