Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

438
Views
What would cause lockfileVersion in package-lock.json to decrease by one?

Bumped the patch version in a package.json (manually, edited file). Noted that the lock file had the old version, so I did an npm install to update it. When I did that the lockfileVersion field went from 2 to 1. This seems odd. The docs about lockfileVersion:

An integer version, starting at 1 with the version number of this document whose semantics were used when generating this package-lock.json.

Well that didn't help. So is this change in values of the version a concern? It seems like an odd change, for it to decrease like that. Should I not update the lockfile when I bump the version?

Node v12.16.1, NPM 6.14.10

over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

It's probably just because you used an older npm version than the one that was used the last time the package-lock.json file was changed. Update your npm executable and it should use a greater or equal lockfileVersion now.

over 4 years ago · Santiago Trujillo Report

0

https://docs.npmjs.com/cli/v8/configuring-npm/package-lock-json#lockfileversion

lockfileversion 2 is NPM 7. So one person on my team was using NPM 7 while I was still on 6 (lockfileversion 1).

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!