npm install removes resolved and integrity properties from package-lock.json if installed from cache

[SymbioticKilla]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

If you run npm install with existing package cache inside "node_modules" it creates packages-lock.json without "resolved" and "integrity" properties.

Expected Behavior

"resolved" and "integrity" properties should stay remain after npm install using cache from "node_modules" folder

Steps To Reproduce

1.) Run npm install
2.) package-lock.json is created
3.) node modules are cached inside the project folder under "node_modules" folder
4.) delete package-lock.json and delete one package form "node_modules" folder
5.) Run npm install
6.) package-lock.json is created, but "resolved" and "integrity" properties are removed from each package descriptions inside package-lock.json

Environment

• npm: 8.1.2
• Node.js: 16.3.2
• OS Name: Windows 10
• System Model Name:
• npm config:

; copy and paste output from `npm config ls` here

[giovannipds]

In my case, it removes the resolved entry for a company's remote repository, causing the CI pipeline to fail.

• npm 8.1.3
• node v16.3.0
• Mac OS

[ljharb]

@giovannipds what about with npm v8.5.2?

[giovannipds]

@ljharb thanks for interacting. In my case, the issue was in my repository config, it was misconfigured, that's why my resolveds were being removed. Probably not related to what this ticket is about. What fixed for me:

npm config set registry #YOUR_COMPANY_REGISTRY_URL

[vmasek]

I managed to get proper package-lock.json (with integrity and resolve fields) after:

• cleaning the npm cache npm cache clean -f
• removing node_modules in project folder
• removing the package-lock.json file
• running npm install in now "clean" project folder

[aarowman]

Just ran into this issue on npm 8.19.2 with node v18.12.1.

Cleared the cache and re-ran npm install (slow), then it was ok

[cdpark0530]

I encountered the same issue with nodejs 16.19.1 and npm 8.19.3

[daksh-sagar]

encountered the same issue with node 14.18.0 and npm 8.19.3