Good job on creating a lightweight client. Apollo can be overkill for smaller projects.<p>You should be careful with the name though because it's named the same as the official reference implementation of the backend: <a href="https://github.com/graphql/graphql-js" rel="nofollow">https://github.com/graphql/graphql-js</a>.
Bravo! Despite the fact that it doesn't have caching built in, which isn't needed by everyone, I'm glad to see that the GraphQL ecosystem gets much richer by having alternatives to the fat libraries Apollo and Relay. Well done and thank you!
Just deployed this to production. It was by far the best js client I found for my needs.<p>I would love to see some sort of mutation batching if that's not too far out of the scope of the project. Right now I'm just using a class to build mutations in bulk and send them across in a single POST.
When Javascript projects write "Isomorphic", what do they mean?<p>It certainly isn't isomorphic in the usual sense in Math of a bijection between structures (categories), because even if it were it is a special case of some kind.
I’m all for a lightweight GraphQL client, but does this do any client side caching? Query diffing? Query merging? To me those are the killer features enabled by GraphQL.
I spent a good amount of time getting AWS AppSync to work with different GraphQL clients last week.<p>Looking forward to check out this one.<p>Thanks for sharing!