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.

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

Fix npm v7 / package-lock v2 converter #74

Open
antongolub opened this issue Mar 25, 2021 · 2 comments
Open

Fix npm v7 / package-lock v2 converter #74

antongolub opened this issue Mar 25, 2021 · 2 comments
Labels

Comments

@antongolub
Copy link
Collaborator

npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN audit 400 Bad Request - POST https://registry.npmjs.org/-/npm/v1/security/audits/quick - Bad Request
{
  statusCode: 400,
  error: 'Bad Request',
  message: 'Invalid package tree, run  npm install  to rebuild your package-lock.json'
}

@antongolub antongolub added this to the 2.0.0 milestone Mar 25, 2021
@antongolub antongolub removed this from the 2.0.0 milestone Mar 25, 2021
@antongolub antongolub changed the title Add support for npm v7 / package-lock v2 Fix npm v7 / package-lock v2 converter Mar 25, 2021
@antongolub antongolub added the bug label Mar 25, 2021
@SinaKarimi7
Copy link

@imsnif Is there any updates to fix this?

@imsnif
Copy link
Owner

imsnif commented Dec 12, 2021

No, sorry. I haven't been doing javascript for quite a while now. So unless @antongolub has plans for this, I think it's a no go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants