Switch out @apollo/client for smaller bundle size

I ripped out @apollo/client from @redwoodjs/web and implemented a super basic graphql client on my own instead. I then created two RW apps with the two different graphql clients to compare sizes

With @apollo/client

$ du -s web/dist/
1980    web/dist/

With the custom RW client

$ du -s web/dist/
1084    web/dist/

So almost half the bundle size just by switching out our graphql client. I think it’s worth thinking about what we really need/want to ship by default. With the (hopefully) coming possibility for our users to wire up RW to use whatever gql client they want, maybe we don’t need such an advanced and fully featured client as apollo bundled up with the framework itself.

[jpvajda]

@Tobbe 👋 I was reviewing this issue and though it’s older, it’s still very relevant of a topic for us at Apollo GraphQL, as we’ve had others asking us about the total bundle size of Apollo Client and have raised concerns about it’s size. I’m actually the Staff Product Manager of Apollo Client, and I’d be deeply interested in learning where this particular change is at for RedwoodJS and if there is any specific feedback we could gather from you as it relates to Apollo Client. We’d love to keep Apollo Client as part of the core offering of RedwoodJS, so any feedback you can share would be awesome for us to hear.

I’d be happy to setup some time to discuss further or we can have any async conversation. I’m also including the Client engineering team on this issue as they are always open to feedback and happy to answer any questions.

cc @benjamn @hwillson @brainkim

[NetLancer]

I personally thought about bundle size decrease by swapping for preact, and it appeared that urql claims to have good charasteristics + supports preact,so preact & urql options would be great to have, the solution i’ve been googling for ))