feat!: stream Suspense chunks via declarative shadow dom#442
Closed
jacob-ebey wants to merge 2 commits intopreactjs:mainfrom
Closed
feat!: stream Suspense chunks via declarative shadow dom#442jacob-ebey wants to merge 2 commits intopreactjs:mainfrom
jacob-ebey wants to merge 2 commits intopreactjs:mainfrom
Conversation
🦋 Changeset detectedLatest commit: 7a26be0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Author
|
This doesn't work quite the way I had thought. This won't work but was a fun learning experience. |
Contributor
Author
|
This doesn't work with Suspense semantics, but it did lead to a potential new primitive (Shadow) where it's non-template children render in the order they land allowing OOO streaming semantics within a single view with ZERO JS. Deterministic UI order can be achieved with slot names even on function Wrapper({ children }: { children?: JSX.Children }) {
return (
<Shadow ext="section">
<Shadow.Template>
<p>before</p>
<slot>loading</slot>
<p>after</p>
</Shadow.Template>
{children}
</Shadow>
);
}
async function Component({
children,
delay,
}: {
children?: JSX.Children;
delay: number;
}) {
await new Promise((r) => setTimeout(r, delay * 500));
return <p>resolved {children}</p>;
}<html>
<head></head>
<body>
<h1>Hello, World!</h1>
<Wrapper>
<Component delay={3}>1</Component>
<Component delay={4}>2</Component>
<Wrapper>
<Component delay={2}>1.1</Component>
<Component delay={1}>2.1</Component>
</Wrapper>
</Wrapper>
</body>
</html>HTML lands in chunks denoted below by <html>
<head></head>
<body>
<h1>Hello, World!</h1>
<section>
<template shadowrootmode="open">
<p>before</p>
<slot>loading</slot>
<p>after</p>
</template>
<!--/chunk-->
<section>
<template shadowrootmode="open">
<p>before</p>
<slot>loading</slot>
<p>after</p>
</template>
<p>resolved 2.1</p>
<!--/chunk-->
<p>resolved 1.1</p>
</section>
<!--/chunk-->
<p>resolved 1</p>
<!--/chunk-->
<p>resolved 2</p>
</section>
</body>
</html> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.