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

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

Reproduce the issue with npm 8.1.2 and Node.js 16.3.2 by following the listed npm install steps, using node_modules as the cache. Compare the generated package-lock.json entries after deleting the lockfile and one package; done means resolved and integrity remain in each package description.