improve: Optimised imports from graphql to decrease bundle size #543
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
While integrating graphql-request into a project to replace apollo-client, on analyzing the bundles created by webpack, I saw that
graphql
as a dependency itself is taking up a bit more than 500Kib in the chunk generated by webpack.One of the major pros towards opting for graphql-request was its minimal bundle size, and with just these more specific imports, we end up saving close to 300KiB directly. Projects with webpack 4 and some legacy packages would be able to have these smaller bundles as well with this minor refactor
Screenshots