Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Resumability? #124

Open
renhiyama opened this issue Dec 4, 2022 · 1 comment
Open

Feature Request: Resumability? #124

renhiyama opened this issue Dec 4, 2022 · 1 comment

Comments

@renhiyama
Copy link

renhiyama commented Dec 4, 2022

Can you please take a look at https://qwik.builder.io/ ?
They talk about Resumability feature, and it sounds pretty great, but they currently "build" and expose some different APIs which even makes it incompatible with original react projects... Can we see Resumability feature on nano ssr anytime soon? Preferably the "no build required" route? If possible I want to work with nano to support this feature too ☺️
Lemme know about anything
More info:
https://qwik.builder.io/docs/concepts/resumable/

@Kapelianovych
Copy link

Kapelianovych commented Jun 17, 2023

It may not be possible with the current nano state.

First of all resumability requires the library to be able to fetch modules on demand which requires a special compilation to generate such modules. Qwik does such loading by propagating events to special handler which is able to determine which module to load. Those modules has to be separated into two pieces: logic and UI. UI shouldn't replace old nodes with identical ones to conduct true resumability. But as far as I know nano even in current state with implemented hydration just generates and replaces a non-interactive DOM tree with the same but interactive DOM tree. The hydrate function is just an alias to the render.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants