[BUG] Production installations resolves development dependencies

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 npm installs the dependencies from package.json with the flag --production it tries to resolve the other dependencies as well but than cause the installation to fail with an error because the dependencies might not be available in the environment.

An example: You have some private build tools in you devDependencies that aren't required for running the project in production and are also not available.

Expected Behavior

Installation with --production should only resolve the necessary dependencies and ignore the other ones.

Steps To Reproduce

1. Setup package.json
2. Install private package as dev dependency
3. Log out from registry – so that you aren't able to access the private package anymore (or use an environment in which you aren't logged in)
4. Remove node_modules if needed
5. Run npm install --production

Environment

• npm: 8
• Node.js: 16
• OS Name: macOS / Amazon Linux 2

Start by reproducing the failure with a package.json containing an inaccessible private devDependency, then run npm install --production as described. Trace the production dependency-resolution path and verify that installation succeeds without attempting to resolve unavailable devDependencies.