When dealing with large-scale software, we have to communicate, work, and cooperate with a lot of people. Besides that, we have to deal with the environment we are working with, which may consist of many projects, large or small, external projects, libraries, shared modules, utilities, and many others. Let's not forget that you aren't the only one working on this project, so we need to maintain same dependencies universally to work together!
~A guy on the Internet said and I quote
Before proceeding further, Checkout Step 5.3 in CONTRIBUTIONS.md to know what we're exactly talking about.
If you've already installed/updated packages using npm install or npm update, Follow the steps below to get out of dependency hell and avoid merge conflicts:
-
Ensure package.json and package-lock.json is identical to upstream. You can do so by various methods, we recommend...
- Deleting
package-lock and package json files and download them to your working directory from Upstream repo OR
- COPY and PASTE
package-lock and package json from upstream to your local environment.
-
Finally, Run npm ci in the terminal in root directory of project. Congratulations, We brought you out of Dependendency Hell
This issue will be kept open for discussion!
Before proceeding further, Checkout Step 5.3 in CONTRIBUTIONS.md to know what we're exactly talking about.
If you've already installed/updated packages using
npm installornpm update, Follow the steps below to get out of dependency hell and avoid merge conflicts:Ensure
package.jsonandpackage-lock.jsonis identical to upstream. You can do so by various methods, we recommend...package-lockandpackagejson files and download them to your working directory from Upstream repo ORpackage-lockandpackagejson from upstream to your local environment.Finally, Run
npm ciin the terminal in root directory of project. Congratulations, We brought you out of Dependendency Hell