[4] crypto@1.0.1: This package is no longer supported. It's now a built-in Node module

[PhilETaylor]

Steps to reproduce the issue

npm ci

Expected result

Actual result

npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should

System information (as much as possible)

 npm -v
7.20.6
 node -v
v16.6.2

[ghazal]

Issue confirmed.
Same config:
npm -v
7.20.6
node -v
v16.6.2

[brianteeman]

This can wait until after the release as it is not include in the actual release

[dgrammatiko]

PR: #35198 (combined with another issue for build tools)