[BUG] Invalid local dependency file doesn't fail install process

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 running the npm install command, if in the package.json file exists an invalid path for a local dependency file, the install process doesn't fail as expected.
Example: "dependencies": { "json": "file:json" }

If we specify a local dependency file with invalid path but now with extension tar.gz, the install fails and returns an error message.
Example: "dependencies": { "json": "file:json.tar.gz" }

Note: in both cases the path is invalid, so the files don't exist in the project, because when the file exist it is working as expected.

Expected Behavior

The expected results for any kind of non existing file path, when specifing a local dependency file that doesn't exist, would be to fail the install process and return the error message.

Steps To Reproduce

1. Create an npm project and specify in the package.json file a local dependency file with an invalid path: "dependencies": { "json": "file:json" }.
2. Run the command npm install.
3. See that the install process doesn't fail, and no error message is shown.

Otherwise, if an invalid tar.gz file is specified an expected error is presented:

1. Create an npm project and specify in the package.json file a local dependency file with an invalid path: "dependencies": { "json": "file:json.tar.gz" }.
2. Run the command npm install.
3. See that the install process fails as expected, and an error is shown: npm ERR! enoent ENOENT: no such file or directory, open '...\lodash.tar.gz' npm ERR! enoent This is related to npm not being able to find a file..

Environment

• npm: 8.9.0
• Node.js: 16.15.0

Start by reproducing the behavior with the package.json dependencies shown and compare the file and tar.gz cases while tracing npm install's local dependency handling. Done means every nonexistent local dependency path fails installation with an error, while existing local files continue to install successfully.