Deleting `package-lock.json` to Resolve Conflicts quickly

by

Yes, it can and will affect all the project in really bad way.

  1. if your team does not run npm install after each git pull you all are using different dependencies’ versions. So it ends with “but it works for me!!” and “I don’t understand why my code does not work for you”

  2. even if all the team runs npm install it still does not mean everything is ok. at some moment you may find your project acts differently. in a part that you have not been changing for years. and after (probably, quite painful) debugging you will find it’s because of 3rd level dependency has updated for next major version and this led some breaking changes.

Conclusion: don’t ever delete package-lock.json.

Yes, for first level dependencies if we specify them without ranges (like "react": "16.12.0") we get the same versions each time we run npm install. But we cannot say the same about dependencies of 2+ level deep (dependencies that our dependencies are relying on), so package-lock.json is really important for stability.

In your case you better do next way:

  1. fix conflicts in package.json
  2. run npm install

As easy as it looks. The same to yarn – it fixes lockfile conflict on its own. The only requirement here to resolve all the conflicts in package.json beforehand if any.

Per docs npm will fix merge conflicts in package-lock.json for you.

[Upd from 2021] important! If you use some library already and npm/GitHub account of its maintainer is hacked. And new version with malicious code inside is released. And you have package-lock.json intact. You will be fine. If you drop it you are in trouble.

More Related Contents:

  1. Npm Package Install Problem (found 23 vulnerabilities)
  2. How do I completely uninstall Node.js, and reinstall from beginning (Mac OS X)
  3. Node.js – SyntaxError: Unexpected token import
  4. Sending command line arguments to npm script
  5. Where does npm install packages?
  6. Installing a local module using npm?
  7. What does npm install –legacy-peer-deps do exactly? When is it recommended / What’s a potential use case?
  8. Maximum call stack size exceeded on npm install
  9. Use of @ symbol in Node module names [duplicate]
  10. How do we or can we use node modules via npm with Meteor?
  11. Module not found: Error: Can’t resolve ‘crypto’
  12. Running NPM scripts sequentially
  13. Appending .js extension on relative import statements during Typescript compilation (ES6 modules)
  14. Can I install a NPM package from javascript running in Node.js?
  15. How to use npm module in DENO?
  16. `npm build` doesn’t run the script named “build” in package.json
  17. After installation of Gulp: “no command ‘gulp’ found”
  18. Angular 2 – How to pass URL parameters?
  19. Uncaught ReferenceError: process is not defined
  20. Node.js Port 3000 already in use but it actually isn’t?
  21. How to publish a module written in ES6 to NPM?
  22. Writing npm modules in TypeScript
  23. How to close electron app via javascript?
  24. Fix the upstream dependency conflict installing NPM packages
  25. create-react-app: How do I “npm start” with a specific browser?
  26. Can’t install any NPM package, error 4058
  27. Using Async waterfall in node.js
  28. How to use npm modules in browser? is possible to use them even in local (PC)?
  29. Error installing node-gyp on ubuntu
  30. Cannot create a string longer than 0x1fffffe8 characters in JSON.parse?

Leave a Comment