-
Notifications
You must be signed in to change notification settings - Fork 178
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
Stop bundling GraphQL js #6
Comments
Do we still wanna do this? |
This is more critical now, because parsing actually changed in 0.8.x to support |
Yeah I can def take a look. A couple concerns are people who used print/parser from gql tag who will now be broken. So we will need to plan accordingly. Another idea is to bundle the newer versions of those libs and bundle with webpack2. |
@abhiaiyer91 oh, I was just thinking this could have a dependency (or peer dep) on |
Nice yeah I'll def do that. Issues I'm running into right now is how the parse function has changed. We're getting caught in Max call stacks in tests when we stripLoc. Diving into that will let you know |
I seem to recall something has changed about the |
Any update @abhiaiyer91 ? |
ping @abhiaiyer91, any updates here? |
Sorry totally forgot about this issue. Let me put it on my schedule for today |
We actually had to make some changes to graphql-js recently to make it support Rollup for the Angular integration. So now it should be possible for people to do dead code elimination when using this package, if we remove our own custom bundling! |
Alright so we definitely have an issue stripping the loc field from the AST generated by the graphql parser. The issue here is in the Quick question, why do we |
We do that because if you serialize the query to JSON then we end up with a ton of copies of the query string. Maybe the ast structure changed in a newer version? |
I had the same problem with |
@KordonDev nice! I realized the same about the new AST structure last night! |
This is done, but not released. |
Now that the bundling errors have been fixed we should remove the bundled code from this repo again and test that it still works in react native.
The text was updated successfully, but these errors were encountered: