usePreloadedQuery - should make squigglehub faster

[berekuk]

Based on https://github.com/relayjs/relay-examples/tree/main/issue-tracker-next-v13.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b307460

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
quri-hub	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 30, 2023 6:25pm

3 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
quri-ui	⬜️ Ignored (Inspect)	Visit Preview		Jul 30, 2023 6:25pm
squiggle-components	⬜️ Ignored (Inspect)	Visit Preview		Jul 30, 2023 6:25pm
squiggle-website	⬜️ Ignored (Inspect)	Visit Preview		Jul 30, 2023 6:25pm

[berekuk]

This is ready. No /api/graphql queries on client side on page load, feels significantly faster.

The pattern for loading data in Next.js pages is a bit verbose, so I added some documentation notes.

Loading states are still there; my understanding is that in many cases Next.js is able to load some parts of the UI immediately thanks to suspense and streaming, so it works as intended. The client waits for the server to send page contents, but doesn't hit the API itself.

[OAGr]

Seems like things load a fair bit faster, happy to see that.

Most of the code seems like it's just adding this pattern around. I'm trusting you on this pattern.