Is 'lockfileVersion: 2' in package-lock.json from npm 7 compatible with older versions of npm?

npm version lockfile
Thaun_ picture Thaun_ · Feb 11, 2021 · Viewed 16.2k times · Source

I was wondering if the new lockfileVersion 2 was backwards compatable with older versions of NPM.

Now since NPM 7 is released, a new package-lock.json file is regenerated to a different structure. From lockfileVersion 1 to 2.

I would be guessing if it was supported, if adding new packages from old npm lockfile to the new one would not be compatible.

Answer

apollo-coder picture apollo-coder · Feb 13, 2021

Yes it is, I tried it myself. And here's a remark from the blog:

One change to take note of is the new lockfile format, which is backwards compatible with npm 6 users.

source: https://github.blog/2021-02-02-npm-7-is-now-generally-available/#changes-to-the-lockfile

Related questions

Is there a way to get version from package.json in nodejs code?

Is there a way to get the version set in package.json in a nodejs app? I would want something like this var port = process.env.PORT || 3000 app.listen port console.log "Express server listening on port %d in %s …

Read More
How can I specify the required Node.js version in package.json?

I have a Node.js project that requires Node version 12 or higher. Is there a way to specify this in the packages.json file, so that the installer will automatically check and inform the users if they need to upgrade?

Read More
Node - was compiled against a different Node.js version using NODE_MODULE_VERSION 51

I am running a node application on terminal. Have recently upgraded to node v8.5.0, but am getting this error: Error: The module '/tidee/tidee-au/packages/tidee-au-server/node_modules/bcrypt/lib/binding/bcrypt_lib.node' was compiled against a different …

Read More