A issue about multiple versions of dependencies

[blueMountain007]

Our project is a mono repo managed with nx, The file hierarchy is as follows:

• package.json
  • [email protected]
  • payload（It depends on [email protected] and graphql-type-json）
  • ...
• apps
  • app1(It depends on payload, and payload depends on [email protected])
  • app2(Depends on [email protected])
  • app3(Depends on [email protected])
  • ...

After executing the command npm install, the hierarchical relationship of dependencies is as follows:

• node_modules
  • [email protected]
  • payload
    • node_modules
      • [email protected]
  • graphql-type-json

My problem description:

1. App1 used [email protected] before, so there is no need to upgrade the graphql version. But [email protected] depends on [email protected]

2. Except for app1, other projects still depend on [email protected], so the graphql version of the entire project cannot be upgraded to 16.8.1;

3. After the dependency is installed, graphql-type-json in app1 is at the same level as the payload, and then references [email protected], while the payload references [email protected], resulting in two different ones being used inside the payload. version of graphql, which causes the payload to not work properly.

Other
"nx": "14.8.9"
"payload": "2.3.1"