Open jashan777 opened 10 months ago
seems to be a npm version issue as the issue doesn't appear in npm versions >=8.19.3 & node>= 16.19.0
Yeah, this is more an npm issue than npm-check-updates. We don't touch the package lock file, and we don't have control over how the modules are installed.
Yeah, this is more an npm issue than npm-check-updates. We don't touch the package lock file, and we don't have control over how the modules are installed.
The changes are reverted if one remove the node_modules folder again and do npm i , but suprisingly npm-check-updates version <= 16.3.0 works just fine and doesnt cause this issue.
Yes, that does seem strange. I wonder what changed between 16.3.0 and 16.4.0 that changed npm's install behavior.
npm-check-updates
node >= 14.14
Steps to Reproduce
node version - v14.20.0 npm version - v6.14.17 os - windows 11 or macos ventura 13.4
npm i
npm i
again.package-lock.json will change.
The changes are reverted if node_module folder is deleted and
npm i
is done.ScreenShots Below are the changes in package-lock.json after second
![Screenshot 2023-11-04 121008](https://github.com/raineorshine/npm-check-updates/assets/49744054/e2ab2e72-d195-4e07-a258-95f265e6b72b)
npm i
first npm i : package-lock.json packageFirst.txt.txt
second npm i: package-lock.json packageSecond.txt.txt