NX should not use package.json for in-repo dependencies

[RobertDiebels]

Current Behavior

Most tools correctly assume that the dependencies listed in a package.json are located on a artifact registry which need to be retrieved.
As a result they will attempt to retrieve those dependencies from the specified artifact registry. Some of these tools will fail gracefully, and others not so much. For instance, any tool using pnpm update --recursive on a NX mono-repo will crash (not so gracefully).

In either case, these tools correctly assume that the listed dependencies should be in a artifact registry. This means that NX is misusing the package.json to declare in-repo dependencies between projects.

Expected Behavior

I would expect that NX:

• Does not use the package.json file to list in-repo dependencies, unless the in-repo projects are published and retrieved (which would be odd.. but possible).
• Provides some other means of tracking in-repo dependencies (for instance through the project.json).

GitHub Repo

No response

Steps to Reproduce

1. Run pnpm update --recursive on a mono-repo with in-repo dependencies.

Nx Report

N/A

Failure Logs

N/A

Package Manager Version

pnpm@9.3.0

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

No response