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
  • graphql@15.8.0
  • payload（It depends on graphql@16.8.1 and graphql-type-json）
  • ...
• apps
  • app1(It depends on payload, and payload depends on graphql@16.8.1)
  • app2(Depends on graphql@15.8.0)
  • app3(Depends on graphql@15.8.0)
  • ...

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

• node_modules
  • graphql@15.8.0
  • payload
    • node_modules
      • graphql@16.8.1
  • graphql-type-json

My problem description:

1. Except for app1, other projects still depend on graphql@15.8.0, so the graphql version of the entire project cannot be upgraded to 16.8.1;

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

3. Expect both payload and graphql-type-json to use the same graphql@16.8.1

Other
"nx": "14.8.9"