Reactjs Question posted in
The new location for the React Documentation can be found here.

Reactjs – Same node version, same npm version but different package.lock file

We have a react project. We are using the same node version (18.16.1) and the same npm version (9.5.1) as a whole team. When I run npm install after cloning the repo, I get a different package-lock file. Why is that happening?

One of the differences:

enter image description here

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    @a.deshpande012's answer was okay when I did install but IMHO, probably it was going to give another error if I install another package.

    The fix was aligning .npmrc file with others.


  2. 0

    Take a look at this question.

    To summarize, npm install is not guaranteed to be a deterministic, reproducible build. If you want exact reproducibility, you should use npm ci to install dependencies.

    Your package-lock.json is automatically generated/updated when you install or update dependencies, and reflects the currently installed packages for that project. So the reason the package-lock.json is different across machines is due to the nondeterminism of npm install.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search