#4048 (Issues after pulling lino_react)
by Luc Saffre · in Developers · assigned to Luc Saffre
Kokkuvõte
After having done "git pull" in react, I say "npm install" and it says:
up to date, audited 988 packages in 3s
found 0 vulnerabilities
npm notice
npm notice New minor version of npm available! 7.6.3 -> 7.7.3
npm notice Changelog: github.com/npm/cli/releases/tag/v7.7.3
npm notice Run npm install -g npm@7.7.3 to update!
npm notice
Children
Kommentaarid
- 5 aastat, 6 kuud ago by Luc Saffre about #4048 (Issues after pulling lino_react) : The issues literally "disappeared" when I tried to show them to Sharif. Maybe the site data had to renew? Some parts of npm package management are still surprising to me...
- 5 aastat, 7 kuud ago by Sharif Mehedi about #4048 (Issues after pulling lino_react) : This should not be a problem. From what I understand package-lock.json is kind of a reflection of package.json. npm uses package-lock to resolve the dependencies tree faster. As npm updates it gets better in understanding how to resolve the dependencies faster, that's why the changes. I'd suggest tha...
- 5 aastat, 7 kuud ago by Luc Saffre about #4048 (Issues after pulling lino_react) : I see that "npm install" has updated my package-lock.json file. Is that normal? Also after saying "sudo npm install -g npm@7.7.3", my package-lock.json file is quite different from the file in the repository. Should the package-lock.json file be in .gitignore?