Question

151

Npm install throws warn old lockfile error

rated 0 times [ 155] [ 4] / answers: 1 / hits: 10418 / 2 Years ago, tue, december 28, 2021, 12:00:00

npm 8.1.2 | node 16.13.1

Npm throws the error below when I use npm install, I believe it is about versions but not sure, I installed npm version 7.19.1 but still got the same error, any idea why and how to solve this issue?

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 deprecated [email protected]: Please update to ini >=1.3.6 to avoid a prototype pollution issue

npm WARN deprecated [email protected]: this library is no longer supported

npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)

npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.

npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142

npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)

npm WARN deprecated [email protected]: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the 

future

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

deonkalvinw

Add To Favorites

Follow

Total Points: 409

Total Questions: 96

Total Answers: 89

Location: Saint Pierre and Miquelon

Member since Sun, Nov 27, 2022

2 Years ago

deonkalvinw questions

1 Handling UI State in Remix.run

Sun, Feb 6, 22, 00:00, 2 Years ago

1 moving between section page using next and previous button in javascript

Tue, Dec 28, 21, 00:00, 2 Years ago

1 React Horizontal Scrolling cards with Arrows on top

Sun, Aug 22, 21, 00:00, 3 Years ago

1 How to pass state between routes in NEXT JS?

Sun, Mar 7, 21, 00:00, 3 Years ago

1 Why is this Hello, World! JavaScript code fragment recognized as an acceptable program instruction?

Tue, Jan 21, 20, 00:00, 4 Years ago

View All

answered 2 Years ago ronans · Accepted Answer

That means that the package-lock.json file was created while performing an npm install with an npm version less than 7.

npm 7 has changed not only the format of package-lock.json, but also how it handles peer dependencies. When you upgrade to a newer npm version ( >=7 ) make sure to test everything properly with a freshly checked out repo that still has the old file version.

You can resolve the issue (when all testing went well) by committing and pushing the package-lock.json in the new format.