-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attempted Import errors when migrating to Apollo 3.x #8663
Comments
@in15 Have you tried upgrading the |
Hi @benjamn - good suggestion. I upgraded graphql to the latest version, 15.5.1, and re-attempted. Same issues, unfortunately.
|
@benjamn many people are stuck on graphql v14 because the apollo cli isn't compatible with v15: apollographql/apollo-tooling#2232 |
Related?: I got this when upgrading from Apollo client 3.3.21 to 3.4.9. My graphql verison is 15.5.1. |
For those who come here later having this issue You can set |
Intended outcome:
Migrating from @apollo/react-hooks and other packages to @apollo/client (3.4.7). After following migration guide, my intent was for things to work.
Actual outcome:
Followed the migration guide.
Have graphql 14.7.0 included in my package
node_modules is populated as expected.
When running the dev server, I see the following:
When inspecting my local node_modules, I see that
visit
andBREAK
are exported by thegraphql
package.How to reproduce the issue:
Versions
3.4.7
and attempted 3.3.20
The text was updated successfully, but these errors were encountered: