Is your feature request related to a problem? Please describe.

• Many projects include a JS target. Supporting JS targets will increase Apollo’s viability when being considered for multi-platform projects.
• It is not straightforward to use Apollo in projects that include a JS target. This is due to the apollo-runtme-kotlin artifact, which can’t be used in commonMain. One workaround is

I would love to have native examples of all the state systems in https://snack.expo.io/

This is a bit of a haul, help needed.

See the-road-to-graphql/fullstack-apollo-express-postgresql-boilerplate#5 for users domain. Maybe someone wants to add tests for the messages domain too.

The docstring of expectOne says

   /**
     * Expect that a single  has been made which matches the given URL, and return its
     * mock.
     *
     * If no such  has been made, or more than one such  has been made, fail with an
     

Feature Request

Currently the React Native sample app is pretty much a bare-bones app with no styling or UI.

This could be a good first issue for someone to contribute to the repo and make the sample app nicer to look at.

An improve to the layout of the devtool could definitely improve user experience. Lets make sure the devtool is utilizing the space better.

Graphback comes with number of templates (see repo templates directory.) Over the last month we seen increased demand to Nest.js framework and it wil.be good to be able to have some nest.js backend template