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

277
Views
npm ci not throwing error despite mismatch

I've been reading about npm ci lately, and have been trying to understand it fully, but I'm running into an issue.

it is strictly written in npm docs that

If dependencies in the package lock do not match those in package.json, npm ci will exit with an error, instead of updating the package lock.

However for me, it just never exits with an error, and always succeeds, not matter how my package-lock.json differs from my package.json. I've tried updating my package-lock.json manually with a non-existing version (v30.7.0) for zustand, I've tried completely removing any mention of zustand from my package-lock.json, and I've tried manually downgrading it to v3.0.0. Every single time, npm ci succeeds and installs zustand v3.7.0 successfully.

Either I'm not fully getting what it's supposed to do, or it's just not functioning correctly, I'd really love for someone to clear that up for me. Thanks!

about 4 years ago · Juan Pablo Isaza
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!