[BUG] `npm update` deletes name property of @scoped workspace dependencies from the package-lock

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

When using workspaces some of the workspace names may be scoped. When this is the case the package-lock includes the "name" property of the scoped, locally resolved packages. Running npm update removes the name properties, causing resolution issues later during release, after running npm install after an npm version.

Expected Behavior

The command npm update preserves the name property in the package-lock.json when present.

Steps To Reproduce

1. Using npm@8.5.3 with Node 16
2. Run:

git clone https://github.com/riovir/npm-update-deleted-name-reprod.git
cd npm-update-deleted-name-reprod
npm ci
npm update
git diff

3. Notice how the name props are missing.
4. Note that running npm install puts them back.

Environment

• npm: 8.5.3
• Node.js: 16.14.0
• OS Name: Windows 10 Pro

Clone riovir/npm-update-deleted-name-reprod and run the listed npm ci, npm update, and git diff steps to reproduce the package-lock.json change. Trace the npm update handling for scoped workspace dependencies and verify that the name properties remain after updating, while npm install continues to restore them when needed.