You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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;
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.
Expect both payload and graphql-type-json to use the same [email protected]
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Our project is a mono repo managed with nx, The file hierarchy is as follows:
[email protected]
payload
(It depends on[email protected]
andgraphql-type-json
)payload
, andpayload
depends on[email protected]
)[email protected]
)[email protected]
)After executing the command
npm install
, the hierarchical relationship of dependencies is as follows:[email protected]
payload
[email protected]
graphql-type-json
My problem description:
Except for app1, other projects still depend on
[email protected]
, 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 references[email protected]
, while the payload references[email protected]
, resulting in two different ones being used inside thepayload
. version ofgraphql
, which causes the payload to not work properly.Expect both
payload
andgraphql-type-json
to use the same[email protected]
Other
"nx": "14.8.9"
Beta Was this translation helpful? Give feedback.
All reactions