You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way Graffle is currently built leads to dragging in all/most of graphql package even when its features are not be used (for example: send a document as a string to a GraphQL schema over HTTP).
Ideas / Proposed Solution(s)
Turn Memory transport into an extension so that its reliance on "heavy" parts of graphql (like execute which alone is 350+kb) is not forced into core
Audit graphql utility imports for accidental dragging in of many KBs
The text was updated successfully, but these errors were encountered:
Perceived Problem
The way Graffle is currently built leads to dragging in all/most of
graphql
package even when its features are not be used (for example: send a document as a string to a GraphQL schema over HTTP).Ideas / Proposed Solution(s)
graphql
(likeexecute
which alone is 350+kb) is not forced into coregraphql
utility imports for accidental dragging in of many KBsThe text was updated successfully, but these errors were encountered: