-
Notifications
You must be signed in to change notification settings - Fork 10
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
add full client API support for Apollo client in plugin-graphql (as ESM) #535
Comments
Looks like there may be an RC we can opt into that might resolve our issues. 🤞 |
Tracking against a couple more ESM migrations |
In light of needing #532 as part of #576 and the fact that as v3.4 Apollo should support all of ESM, might be worth working on this now. |
Better diff, since I think the branch got deleted? Or else I may still have it locally. I think this can be looked into, but maybe better to wait until after #815 is merged first and after #537 ? We will need to lift deps of deps into the import map, and right now that import map is being managed manually. 😮💨 |
Per #952 / #1157 , we have marked this plugin specifically as read only and so mutations are not really in scope |
Type of Change
Summary
As part of introducing the GraphQL plugin in #487, for various reasons, it wasn't possible to support @apollo/client completely, and so only a minimal API surface is available right now, essentially consisting of just a
query
method taking two params;query
andvariables
.Details
The main issue was due to ESM handling as I don't think all of Apollo's dependencies, including transitive, are fully ESM compliant.
This is an excerpt from the linked issue
The text was updated successfully, but these errors were encountered: