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.

Intended outcome:
This is more a docs problem more than anything. The docs include a recipe for using TransferHttpCacheModule to cache requests when using SSR but it does not work as the module does not support POST requests and has no intention to support it. See [here](https://git

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.

Problem

All test files have the following naming convention:

/tests/*Test.ts

Examples:

• KnexDbDataProviderTest.ts
• CRUDServiceTest.ts
• createInMemoryFilterPredicateTest.ts

It is difficult to differentiate a test file from a regular module file at a glance, for example:

createInMemoryFilterPredicateTest.ts compared to createInMemoryFilterPredicate.ts.

Sol