My plan for migrating micro-graphql-react to Svelte was to fork the repo, then use a rusty machete to hack away the complicated bullshit I spent months adding for Suspense support. That'd leave it 98% React agnostic.
Then swap out React, for Svelte.
It appears to work 😏 🥳 🍺
Then swap out React, for Svelte.
It appears to work 😏 🥳 🍺
The main challenge was ... webpack. If webpack doesn't have .mjs at the front of the extensions array, bad things happen to the writeable store, coming from
var internal = require('../internal');
(webpack hard codes undefined)
/cc @Rich_Harris - maybe add a warning?
var internal = require('../internal');
(webpack hard codes undefined)
/cc @Rich_Harris - maybe add a warning?
And that's it. Now begins the real work, of migrating all the tests from React over to Svelte.
If you're by chance one of the few users of the original react version, don't worry - I'll still be supporting it.
If you're by chance one of the few users of the original react version, don't worry - I'll still be supporting it.
It feels SO good to have the original, non-Suspense version of my GraphQL client back. It's much simpler, and easier to reason about; it's like a breath of fresh air.
And naturally it'll still have preload capability. You don't need Suspense to avoid waterfalls 😉
And naturally it'll still have preload capability. You don't need Suspense to avoid waterfalls 😉
• • •
Missing some Tweet in this thread? You can try to
force a refresh
