Can't resolve `graphql-ws` from `@graphiql/toolkit/esm/create-fetcher`
See original GitHub issueSeems like the recent release of @graphiql/toolkit
has broken some of our tests. Maybe due to a missing dependency?
Module not found: Error: Can't resolve 'graphql-ws' in '/tmp/backstage-e2e-Z2eQgF/test-app/node_modules/@graphiql/toolkit/esm/create-fetcher'
error Command failed with exit code 1.
From https://github.com/backstage/backstage/runs/6420680730?check_suite_focus=true
Issue Analytics
- State:
- Created a year ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
[create-app] Module not found: Error: Can't resolve 'graphql-ws'
Expected Behavior Backstage from npx @backstage/create-app should start up using yarn dev without any errors Actual Behavior After starting ...
Read more >graphql-ws - npm
In Explorer Settings, click "Edit" for "Connection Settings" and select graphql-ws under "Implementation". Client usage with GraphiQL.
Read more >Migrating to Apollo Server 4 - Apollo GraphQL Docs
This packaging structure means that new integration package releases are lockstep versioned to Apollo Server itself, making it challenging to support major ...
Read more >Compile error with a lot of errors from webpack - Stack Overflow
I am receiving error, compiling graphql doesn' ...
Read more >Subscriptions and Live Queries - Real Time with GraphQL
Once the AsyncIterator publishes a value (the payload or event), the optional resolve function on the selected subscription root field is called ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sure - I can take a look at this tomorrow.
@thomasheyenbrock, thinking the dynamic import is probably nicer right? not sure theres a need for multiple packages if we can do it in transparent way.