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
{{ message }}
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
Run yarn build, followed by node dist/app.js. It should print a GraphQLErrorExt. The issue is that only one instance of "graphql" may be bundled, but when inspecting dist/app.js, graphql seems to be imported twice:
L32 var graphql_1 = __fusereq(3);
L107 var graphql_mjs_1 = __fusereq(11);
The only solution seems to be to add "graphql" to the list of ignored dependencies in FuseBox' configuration, and installing it separately.
How come graphql is imported as two separate instances instead of one, and is this preventable?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Minimal example project: https://github.com/draoncc/FuseBox-GraphQL-Apollo-CoreSchema-issue-example
Run
yarn build
, followed bynode dist/app.js
. It should print aGraphQLErrorExt
. The issue is that only one instance of "graphql" may be bundled, but when inspecting dist/app.js, graphql seems to be imported twice:The only solution seems to be to add "graphql" to the list of ignored dependencies in FuseBox' configuration, and installing it separately.
How come graphql is imported as two separate instances instead of one, and is this preventable?
The text was updated successfully, but these errors were encountered: