@voidzerodev@rolldown_rs With the bottom right config, are dynamic imports not split anymore? What if I want a specific dependency to be code-split, while keeping dynamic imports split?
@dan_abramov2 I view React as primarily a client-focused library, and RSC gives us the option to render parts of the components tree off the client: in the server or at build time.
In other words Server Components could be called Offloaded Components (or ROC).
@ematipico You'd have to implement request deduplication, caching, revalidation, loading states, error handling, retries, react suspense integration, etc.
Of course you can do it yourself for very basic needs but it's not worth it otherwise.
@dan_abramov Sure, but if you already have a codebase using react-router, you could adopt nextjs, then adopt the nextjs router later when time permits.
Migrating to a different router is quite a big hurdle, and shouldn't be a blocker.
@dan_abramov What if I write it like this?
<Toggle>
{() => <Details note={note} />}
</Toggle>
would the server still send the rendered results?
@dan_abramov Okay, that's not what I'd expect, I may want to avoid fetching data unnecessarily in Details.
What if Toggle never ever renders `children` or other elements passed to it via other props?
Does the server still pass the rendering results of those components to Toggle?
@dan_abramov We use linaria, not the atomic part, just css``, so the styles get extracted as separate stylesheets, and you end up with a class name.
It's lovely, but it can be buggy/slow, so there's room for disruption.
https://t.co/0ag9351Bq4
https://t.co/nygsD1Xbzp
https://t.co/5XwHElTXi8