A issue about multiple versions of dependencies #5540
Closed
blueMountain007
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Our project is a mono repo managed with nx, The file hierarchy is as follows:
graphql@15.8.0
graphql@16.8.1
andgraphql-type-json
)payload
, and payload depends ongraphql@16.8.1
)graphql@15.8.0
)graphql@15.8.0
)After executing the command
npm install
, the hierarchical relationship of dependencies is as follows:graphql@15.8.0
graphql@16.8.1
graphql-type-json
My problem description:
App1 used
payload@1.11.1
before, so there is no need to upgrade thegraphql
version. Butpayload@2.3.1
depends ongraphql@16.8.1
Except for app1, other projects still depend on
graphql@15.8.0
, so thegraphql
version of the entire project cannot be upgraded to 16.8.1;After the dependency is installed,
graphql-type-json
in app1 is at the same level as thepayload
, and then referencesgraphql@15.8.0
, while the payload referencesgraphql@16.8.1
, 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"
Beta Was this translation helpful? Give feedback.
All reactions