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

Implement basic stylesheet Resources for react-dom #25060

Merged
merged 12 commits into from
Aug 12, 2022

Conversation

gnoff
Copy link
Collaborator

@gnoff gnoff commented Aug 7, 2022

Implement basic support for "Resources". In the context of this PR, the only thing that is currently a Resource are

<link rel="stylesheet" precedence="some-value" ...>

Resources can be rendered anywhere in the react tree, even outside of normal parenting rules, for instance you can render a resource before you have rendered the <html><head> tags for your application. In the stream we reorder this so the browser always receives valid HTML and resources are emitted either in place (normal circumstances) or at the top of the <head> (when you render them above or before the <head> in your react tree)

On the client, resources opt into an entirely different hydration path. Instead of matching the location within the Document these resources are queried for in the entire document. It is an error to have more than one resource with the same href attribute.

The use of precedence here as an opt-in signal for resourcifying the link is in preparation for a more complete Resource implementation which will dedupe resource references (mutliple will be valid), hoist to the appropriate container (body, head, or elsewhere), order (according to precedence) and Suspend boundaries that depend on them. More details will come in the coming weeks on this plan.

This feature is gated by an experimental flag and will only be made available in experimental builds until some future time.

@sizebot
Copy link

sizebot commented Aug 7, 2022

Comparing: 32baab3...3d56c0e

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name +/- Base Current +/- gzip Base gzip Current gzip
oss-stable/react-dom/cjs/react-dom.production.min.js = 134.28 kB 134.28 kB +0.03% 42.93 kB 42.94 kB
oss-experimental/react-dom/cjs/react-dom.production.min.js +0.36% 139.84 kB 140.35 kB +0.41% 44.55 kB 44.74 kB
facebook-www/ReactDOM-prod.classic.js = 474.44 kB 474.44 kB +0.02% 84.86 kB 84.87 kB
facebook-www/ReactDOM-prod.modern.js = 459.68 kB 459.68 kB = 82.62 kB 82.62 kB
facebook-www/ReactDOMForked-prod.classic.js = 474.44 kB 474.44 kB +0.02% 84.86 kB 84.87 kB

Significant size changes

Includes any change greater than 0.2%:

Expand to show
Name +/- Base Current +/- gzip Base gzip Current gzip
oss-experimental/react-dom/cjs/react-dom-static.node.production.min.js +1.65% 39.59 kB 40.25 kB +1.64% 13.50 kB 13.72 kB
oss-experimental/react-dom/cjs/react-dom-server.node.production.min.js +1.65% 39.63 kB 40.28 kB +1.68% 13.50 kB 13.72 kB
oss-experimental/react-dom/cjs/react-dom-server-legacy.node.production.min.js +1.58% 39.38 kB 40.00 kB +1.59% 12.99 kB 13.20 kB
oss-experimental/react-dom/cjs/react-dom-server-legacy.browser.production.min.js +1.51% 35.54 kB 36.08 kB +1.74% 11.80 kB 12.01 kB
oss-experimental/react-dom/umd/react-dom-server-legacy.browser.production.min.js +1.50% 35.65 kB 36.19 kB +1.84% 11.92 kB 12.14 kB
oss-experimental/react-dom/cjs/react-dom-static.browser.production.min.js +1.49% 36.03 kB 36.57 kB +1.63% 12.42 kB 12.62 kB
oss-experimental/react-dom/cjs/react-dom-server.browser.production.min.js +1.49% 36.15 kB 36.69 kB +1.65% 12.46 kB 12.66 kB
oss-experimental/react-dom/umd/react-dom-server.browser.production.min.js +1.48% 36.26 kB 36.79 kB +1.61% 12.57 kB 12.78 kB
facebook-www/ReactDOMServerStreaming-prod.modern.js +1.46% 83.52 kB 84.74 kB +0.97% 17.61 kB 17.78 kB
facebook-www/ReactDOMServer-prod.modern.js +1.36% 80.54 kB 81.63 kB +0.91% 16.80 kB 16.95 kB
facebook-www/ReactDOMServer-prod.classic.js +1.31% 83.47 kB 84.56 kB +0.94% 17.40 kB 17.56 kB
oss-stable-semver/react-dom/cjs/react-dom-server.node.production.min.js +1.30% 39.13 kB 39.64 kB +1.20% 13.31 kB 13.47 kB
oss-stable/react-dom/cjs/react-dom-server.node.production.min.js +1.29% 39.16 kB 39.66 kB +1.20% 13.33 kB 13.49 kB
oss-experimental/react-dom/cjs/react-dom-static.node.development.js +1.24% 246.47 kB 249.53 kB +0.90% 59.67 kB 60.20 kB
oss-experimental/react-dom/cjs/react-dom-server.node.development.js +1.24% 246.51 kB 249.57 kB +0.90% 59.57 kB 60.10 kB
oss-experimental/react-dom/cjs/react-dom-static.browser.development.js +1.24% 244.61 kB 247.64 kB +0.92% 59.45 kB 59.99 kB
oss-experimental/react-dom/umd/react-dom-server.browser.development.js +1.24% 257.31 kB 260.48 kB +0.81% 60.38 kB 60.86 kB
oss-experimental/react-dom/cjs/react-dom-server.browser.development.js +1.23% 245.31 kB 248.33 kB +0.92% 59.64 kB 60.19 kB
oss-stable-semver/react-dom/cjs/react-dom-server-legacy.node.production.min.js +1.21% 38.88 kB 39.35 kB +1.33% 12.80 kB 12.97 kB
oss-stable/react-dom/cjs/react-dom-server-legacy.node.production.min.js +1.21% 38.90 kB 39.37 kB +1.32% 12.82 kB 12.99 kB
oss-experimental/react-dom/umd/react-dom-server-legacy.browser.development.js +1.21% 258.37 kB 261.49 kB +0.82% 60.24 kB 60.74 kB
oss-experimental/react-dom/cjs/react-dom-server-legacy.browser.development.js +1.21% 246.35 kB 249.32 kB +0.89% 59.52 kB 60.05 kB
oss-experimental/react-dom/cjs/react-dom-server-legacy.node.development.js +1.20% 248.06 kB 251.03 kB +0.88% 59.99 kB 60.52 kB
oss-stable-semver/react-dom/cjs/react-dom-server.node.development.js +1.17% 244.94 kB 247.81 kB +0.90% 59.14 kB 59.67 kB
oss-stable/react-dom/cjs/react-dom-server.node.development.js +1.17% 244.96 kB 247.83 kB +0.90% 59.16 kB 59.69 kB
facebook-www/ReactDOMServerStreaming-dev.modern.js +1.17% 246.59 kB 249.47 kB +1.00% 58.65 kB 59.24 kB
oss-stable-semver/react-dom/umd/react-dom-server.browser.development.js +1.16% 255.65 kB 258.62 kB +0.81% 59.95 kB 60.43 kB
oss-stable/react-dom/umd/react-dom-server.browser.development.js +1.16% 255.67 kB 258.64 kB +0.81% 59.97 kB 60.46 kB
oss-stable-semver/react-dom/cjs/react-dom-server.browser.development.js +1.16% 243.74 kB 246.57 kB +0.92% 59.21 kB 59.75 kB
oss-stable/react-dom/cjs/react-dom-server.browser.development.js +1.16% 243.76 kB 246.59 kB +0.92% 59.23 kB 59.78 kB
facebook-www/ReactDOMServer-dev.modern.js +1.15% 251.01 kB 253.89 kB +0.92% 59.70 kB 60.25 kB
oss-stable-semver/react-dom/umd/react-dom-server-legacy.browser.development.js +1.13% 256.71 kB 259.62 kB +0.81% 59.83 kB 60.31 kB
oss-stable/react-dom/umd/react-dom-server-legacy.browser.development.js +1.13% 256.73 kB 259.65 kB +0.81% 59.85 kB 60.33 kB
oss-stable-semver/react-dom/cjs/react-dom-server-legacy.browser.development.js +1.13% 244.78 kB 247.56 kB +0.88% 59.08 kB 59.60 kB
oss-stable/react-dom/cjs/react-dom-server-legacy.browser.development.js +1.13% 244.80 kB 247.58 kB +0.88% 59.10 kB 59.62 kB
oss-stable-semver/react-dom/cjs/react-dom-server-legacy.node.development.js +1.13% 246.49 kB 249.26 kB +0.83% 59.57 kB 60.07 kB
oss-stable/react-dom/cjs/react-dom-server-legacy.node.development.js +1.13% 246.51 kB 249.29 kB +0.84% 59.59 kB 60.09 kB
facebook-www/ReactDOMServer-dev.classic.js +1.12% 257.67 kB 260.55 kB +0.86% 61.13 kB 61.65 kB
oss-stable-semver/react-dom/umd/react-dom-server.browser.production.min.js +1.10% 35.81 kB 36.21 kB +1.22% 12.42 kB 12.57 kB
oss-stable/react-dom/umd/react-dom-server.browser.production.min.js +1.10% 35.84 kB 36.23 kB +1.22% 12.44 kB 12.59 kB
oss-stable-semver/react-dom/cjs/react-dom-server-legacy.browser.production.min.js +1.10% 35.10 kB 35.48 kB +1.36% 11.64 kB 11.80 kB
oss-stable/react-dom/cjs/react-dom-server-legacy.browser.production.min.js +1.10% 35.12 kB 35.51 kB +1.36% 11.66 kB 11.82 kB
oss-stable-semver/react-dom/umd/react-dom-server-legacy.browser.production.min.js +1.10% 35.21 kB 35.59 kB +1.45% 11.76 kB 11.93 kB
oss-stable/react-dom/umd/react-dom-server-legacy.browser.production.min.js +1.10% 35.23 kB 35.62 kB +1.45% 11.78 kB 11.95 kB
oss-stable-semver/react-dom/cjs/react-dom-server.browser.production.min.js +1.09% 35.71 kB 36.10 kB +1.29% 12.27 kB 12.43 kB
oss-stable/react-dom/cjs/react-dom-server.browser.production.min.js +1.09% 35.73 kB 36.13 kB +1.29% 12.29 kB 12.45 kB
oss-experimental/react-server/cjs/react-server.production.min.js +0.86% 21.34 kB 21.52 kB +1.18% 7.31 kB 7.40 kB
oss-experimental/react-server/cjs/react-server.development.js +0.65% 131.96 kB 132.81 kB +0.53% 33.06 kB 33.23 kB
oss-stable-semver/react-server/cjs/react-server.development.js +0.51% 131.09 kB 131.76 kB +0.44% 32.85 kB 32.99 kB
oss-stable/react-server/cjs/react-server.development.js +0.51% 131.09 kB 131.76 kB +0.44% 32.85 kB 32.99 kB
oss-stable-semver/react-server/cjs/react-server.production.min.js +0.39% 21.01 kB 21.09 kB +0.71% 7.21 kB 7.26 kB
oss-stable/react-server/cjs/react-server.production.min.js +0.39% 21.01 kB 21.09 kB +0.71% 7.21 kB 7.26 kB
oss-experimental/react-dom/cjs/react-dom.production.min.js +0.36% 139.84 kB 140.35 kB +0.41% 44.55 kB 44.74 kB
oss-experimental/react-dom/umd/react-dom.production.min.js +0.36% 139.88 kB 140.38 kB +0.43% 45.21 kB 45.40 kB
oss-experimental/react-noop-renderer/cjs/react-noop-renderer-server.development.js +0.34% 6.16 kB 6.18 kB +0.76% 1.71 kB 1.72 kB
oss-stable-semver/react-noop-renderer/cjs/react-noop-renderer-server.development.js +0.34% 6.16 kB 6.18 kB +0.76% 1.71 kB 1.72 kB
oss-stable/react-noop-renderer/cjs/react-noop-renderer-server.development.js +0.34% 6.16 kB 6.18 kB +0.76% 1.71 kB 1.72 kB
oss-experimental/react-dom/umd/react-dom.profiling.min.js +0.34% 148.74 kB 149.24 kB +0.43% 47.46 kB 47.66 kB
oss-experimental/react-dom/cjs/react-dom.profiling.min.js +0.34% 149.36 kB 149.87 kB +0.45% 46.87 kB 47.08 kB
oss-experimental/react-reconciler/cjs/react-reconciler.production.min.js +0.24% 100.63 kB 100.87 kB +0.23% 30.73 kB 30.80 kB
oss-experimental/react-reconciler/cjs/react-reconciler.profiling.min.js +0.22% 109.52 kB 109.77 kB +0.24% 32.88 kB 32.95 kB

Generated by 🚫 dangerJS against 3d56c0e

@gnoff gnoff force-pushed the float-initial-resources branch 5 times, most recently from 3bf2574 to 545495d Compare August 9, 2022 19:05
@gnoff gnoff marked this pull request as ready for review August 9, 2022 19:44
@gnoff gnoff changed the title implement preamble and postambl for react-dom/server Implement basic stylesheet Resources for react-dom Aug 9, 2022
@@ -242,6 +243,26 @@ export function getChildFormatContext(
return parentContext;
}

export function isPreambleInsertion(type: string): boolean {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this exported?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bad copypasta

type: string,
props: Object,
responseState: ResponseState,
formatContext: FormatContext,
): ReactNodeList {
// Preamble type is nullable for feature off cases but is guaranteed when feature is on
target = enableFloat && isPreambleInsertion(type) ? (preamble: any) : target;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a pattern that I explicitly tried to avoid when refactoring the DOM bindings as part of Fizz and I was planning to do when refactoring the client next.

The old pattern was basically a bunch of abstractions around specific conditions.

Instead of a bunch of isSomething(...) helpers. I structured it fully based on a switch over each kind of value once and from there the code flow determines what to do next.

#21153

In other words, we should not have things like isPreambleInsertion checks and instead always use the control flow that's already there.

Make a special pushStartHTML, pushStartHead etc. or a shared pushStartPreamble (for now) and then call that from within the switch statement. Then you can check the feature flag in there and otherwise call the generic pushStartGenericElement. If the flag is on and you need to fork behavior you can fork pushStartGenericElement and instead you can call the shared inner functions that pushStartGenericElement calls but it's a shared abstraction. However I don't think you need to do that, you can probably just fork the target chunk array. Although that might not work if we do the string thing in the future.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see what you mean now

type: string,
props: Object,
): void {
// Preamble type is nullable for feature off cases but is guaranteed when feature is on
target =
enableFloat && isPostambleInsertion(type) ? (postamble: any) : target;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same thing here. Put this in the existing switch.

@@ -2149,6 +2168,21 @@ function flushCompletedQueues(
// We don't need to check any partially completed segments because
// either they have pending task or they're complete.
) {
allComplete = true;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moving this out of the finally is not correct because if something throws above here, then we won't set this to true and so we don't close the connection if that throw caused all tasks to complete (e.g by being aborted).

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, didn't think of that :)

rootHostContainer,
).querySelectorAll(selector);
if (allLinks.length > 1) {
throw new Error(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should never throw conditionally on __DEV__. If so, it should be console.error instead.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@@ -596,6 +616,9 @@ function popHydrationState(fiber: Fiber): boolean {
if (!supportsHydration) {
return false;
}
if (enableFloat && isHydratableResource(fiber.type, fiber.memoizedProps)) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is always picking this path if it's a hydratable resource, but the push path is sometimes falling through (if there is no matching resource). This means that they can be misbalanced and lead to something weird.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah. That's why you check the state node.

Shouldn't it always just insert a node if it's missing to patch things up rather than leaving it wrong?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it is missing, it gets treated like a hydration error and the client side render will patch things up if possible. Sometimes this won't be possible b/c the link will be out of position and I don't yet have insertion semantics for resources (i.e. if you link is a sibling of it will try to insert into the document which will fail)

The least impactful way to do the insertion would be during the hydration itself which feels sorta wrong b/c i'd be mutating the DOM in the render pass. I know we might do this for preloads at some point but that feels a little out of the norm for a hydration insertion.

If I insert via a normal placement I'm going to need to figure out what to do about resources above and it starts to get messy. I'd rather we have a proper Resources implementation that considers hoisting as a first class concept so I was hoping we could leave this alone as a temporary stop gap

supportsHydration &&
isHydratableResource(node.type, node.memoizedProps)
) {
// This is a crude opt out of Resources from this search algorithm
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just leave this to finding the link tag for now. It'll be fixed once you add the new tag. These reflection helpers are semi-deprecated anyway.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I just not check if the root was manipulated when enableFloat is on?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, that's not an important warning.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok should be good to review

@@ -2139,8 +2159,7 @@ function flushCompletedQueues(
}
largeBoundaries.splice(0, i);
} finally {
completeWriting(destination);
flushBuffered(destination);
let allComplete = false;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can avoid this flag and just use control flow here instead. Just duplicate the completeWriting/flushBuffered in the else branch.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the tradeoff here? Less branching but trivially more code?

// we expect the preamble to be tiny and will ignore backpressure
writeChunk(destination, preamble[i]);
}
preamble.length = 0;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why bother resetting this? The memory will still be retained.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a holdover from when this wasn't gated in a flush once block but agree it can be removed

for (let i = 0; i < postamble.length; i++) {
writeChunk(destination, postamble[i]);
}
postamble.length = 0;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.

responseState: ResponseState,
): ReactNodeList {
// Preamble type is nullable for feature off cases but is guaranteed when feature is on
target = enableFloat && isPreambleInsertion(tag) ? (preamble: any) : target;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't need the isPreambleInsertion() checks. That was the point of creating the pushStartHead helper - now you know that it's a preamble insertion.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

brain broke

responseState: ResponseState,
): ReactNodeList {
// Preamble type is nullable for feature off cases but is guaranteed when feature is on
target = enableFloat && isPreambleInsertion(tag) ? (preamble: any) : target;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.

case 'html':
// Preamble type is nullable for feature off cases but is guaranteed when feature is on
target =
enableFloat && isPostambleInsertion(type) ? (postamble: any) : target;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.

tag: string,
responseState: ResponseState,
): ReactNodeList {
// Preamble type is nullable for feature off cases but is guaranteed when feature is on
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I usually just make the type contain everything you'd expect to exist in the new common state.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was trying to avoid two extra array allocations for non dom (even though no one else is really using it yet I suppose). In the future I'd expect that preamble is not nullable for dom fizz server and is explicitly null for environments that do not support preamble but how would I type that? I guess I could export the preamble type but then I'd probably also need a create function for the preamble itself.

Do you recommend doing it that way?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd just make it required. It's at most two per request, and we don't know if other renderers will end up using it yet.

@gnoff gnoff merged commit 796d318 into facebook:main Aug 12, 2022
@gnoff gnoff deleted the float-initial-resources branch August 12, 2022 20:27
pushAttribute(target, responseState, 'data-rprec', propValue);
} else if (__DEV__) {
throw new Error(
`the "precedence" prop for links to stylehseets expects to receive a string but received something of type "${typeof propValue}" instead.`,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small typo: "stylehseets" -> "stylesheets"

facebook-github-bot pushed a commit to facebook/react-native that referenced this pull request Sep 12, 2022
Summary:
This sync includes the following changes:
- **[c28f313e6](facebook/react@c28f313e6 )**: experimental_use(promise) for SSR ([#25214](facebook/react#25214)) //<Andrew Clark>//
- **[d6f9628a8](facebook/react@d6f9628a8 )**: Remove some RSC subset entry points that were removed in the main entry point ([#25209](facebook/react#25209)) //<Sebastian Markbåge>//
- **[a473d08fc](facebook/react@a473d08fc )**: Update to Flow from 0.97 to 0.122 ([#25204](facebook/react#25204)) //<Jan Kassens>//
- **[7028ce745](facebook/react@7028ce745 )**: experimental_use(promise) for Server Components ([#25207](facebook/react#25207)) //<Andrew Clark>//
- **[bfb65681e](facebook/react@bfb65681e )**: experimental_use(context)([#25202](facebook/react#25202)) //<mofeiZ>//
- **[f0efa1164](facebook/react@f0efa1164 )**: [flow] remove custom suppress comment config ([#25170](facebook/react#25170)) //<Jan Kassens>//
- **[2e7f422fe](facebook/react@2e7f422fe )**: Refactor: its type is Container ([#25153](facebook/react#25153)) //<bubucuo>//
- **[2c2d9a1df](facebook/react@2c2d9a1df )**: [eslint-plugin-react-hooks] only allow capitalized component names ([#25162](facebook/react#25162)) //<Jan Kassens>//
- **[36c908a6c](facebook/react@36c908a6c )**: Don't use the Flight terminology in public error messages ([#25166](facebook/react#25166)) //<Sebastian Markbåge>//
- **[8d1b057ec](facebook/react@8d1b057ec )**: [Flight] Minor error handling fixes ([#25151](facebook/react#25151)) //<Sebastian Markbåge>//
- **[9ff738f53](facebook/react@9ff738f53 )**: [devtools][easy] Fix flow type ([#25147](facebook/react#25147)) //<Tianyu Yao>//
- **[0de3ddf56](facebook/react@0de3ddf56 )**: Remove Symbol Polyfill (again) ([#25144](facebook/react#25144)) //<Ricky>//
- **[b36f72235](facebook/react@b36f72235 )**: Remove ReactFiberFlags MountLayoutDev and MountPassiveDev ([#25091](facebook/react#25091)) //<Samuel Susla>//
- **[b6978bc38](facebook/react@b6978bc38 )**: experimental_use(promise) ([#25084](facebook/react#25084)) //<Andrew Clark>//
- **[11ed7010c](facebook/react@11ed7010c )**: [Transition Tracing] onMarkerIncomplete - Tracing Marker/Suspense Boundary Deletions ([#24885](facebook/react#24885)) //<Luna Ruan>//
- **[b79894259](facebook/react@b79894259 )**: [Flight] Add support for Webpack Async Modules ([#25138](facebook/react#25138)) //<Sebastian Markbåge>//
- **[c8b778b7f](facebook/react@c8b778b7f )**: Fix typo: supportsMicrotask -> supportsMicrotasks ([#25142](facebook/react#25142)) //<kwzr>//
- **[d0f396651](facebook/react@d0f396651 )**: Allow functions to be used as module references ([#25137](facebook/react#25137)) //<Sebastian Markbåge>//
- **[38c5d8a03](facebook/react@38c5d8a03 )**: Test the node-register hooks in unit tests ([#25132](facebook/react#25132)) //<Sebastian Markbåge>//
- **[3f70e68ce](facebook/react@3f70e68ce )**: Return closestInstance in `getInspectorDataForViewAtPoint` ([#25118](facebook/react#25118)) //<Tianyu Yao>//
- **[3d443cad7](facebook/react@3d443cad7 )**: Update fixtures/flight to webpack 5 ([#25115](facebook/react#25115)) //<Tim Neutkens>//
- **[5d1ce6513](facebook/react@5d1ce6513 )**: Align StrictMode behaviour with production ([#25049](facebook/react#25049)) //<Samuel Susla>//
- **[9e67e7a31](facebook/react@9e67e7a31 )**: Scaffolding for useMemoCache hook ([#25123](facebook/react#25123)) //<Joseph Savona>//
- **[19e9a4c68](facebook/react@19e9a4c68 )**: Add missing createServerContext for experimental shared subset ([#25114](facebook/react#25114)) //<Jiachi Liu>//
- **[6ef466c68](facebook/react@6ef466c68 )**: make preamble and postamble types explicit and fix typo ([#25102](facebook/react#25102)) //<Josh Story>//
- **[796d31809](facebook/react@796d31809 )**: Implement basic stylesheet Resources for react-dom ([#25060](facebook/react#25060)) //<Josh Story>//
- **[32baab38f](facebook/react@32baab38f )**: [Transition Tracing] Add Tag Field to Marker Instance ([#25085](facebook/react#25085)) //<Luna Ruan>//
- **[8ef3a7c08](facebook/react@8ef3a7c08 )**: Resume immediately pinged fiber without unwinding ([#25074](facebook/react#25074)) //<Andrew Clark>//
- **[7bcc68772](facebook/react@7bcc68772 )**: Remove argument committedLanes from reappearLayoutEffects and recursivelyTraverseReappearLayoutEffects ([#25080](facebook/react#25080)) //<Samuel Susla>//
- **[ca990e9a7](facebook/react@ca990e9a7 )**: Add API to force Scheduler to yield for macrotask ([#25044](facebook/react#25044)) //<Andrew Clark>//
- **[b4204ede6](facebook/react@b4204ede6 )**: Clean up unused Deletion flag ([#24992](facebook/react#24992)) //<Andrew Clark>//
- **[e193be87e](facebook/react@e193be87e )**: [Transition Tracing] Add Offscreen Test ([#25035](facebook/react#25035)) //<Luna Ruan>//
- **[9fcaf88d5](facebook/react@9fcaf88d5 )**: Remove rootContainerInstance from unnecessary places ([#25024](facebook/react#25024)) //<Sebastian Markbåge>//
- **[80f3d8819](facebook/react@80f3d8819 )**: Mount/unmount passive effects when Offscreen visibility changes ([#24977](facebook/react#24977)) //<Andrew Clark>//

Changelog:
[General][Changed] - React Native sync for revisions 4ea064e...c28f313

Reviewed By: rickhanlonii

Differential Revision: D39384898

fbshipit-source-id: 20b080a53851d6dd9d522c8468dd02aab9ba76db
rickhanlonii pushed a commit that referenced this pull request Oct 6, 2022
Implement basic support for "Resources". In the context of this commit, the only thing that is currently a Resource are

<link rel="stylesheet" precedence="some-value" ...>

Resources can be rendered anywhere in the react tree, even outside of normal parenting rules, for instance you can render a resource before you have rendered the <html><head> tags for your application. In the stream we reorder this so the browser always receives valid HTML and resources are emitted either in place (normal circumstances) or at the top of the <head> (when you render them above or before the <head> in your react tree)

On the client, resources opt into an entirely different hydration path. Instead of matching the location within the Document these resources are queried for in the entire document. It is an error to have more than one resource with the same href attribute.

The use of precedence here as an opt-in signal for resourcifying the link is in preparation for a more complete Resource implementation which will dedupe resource references (multiple will be valid), hoist to the appropriate container (body, head, or elsewhere), order (according to precedence) and Suspend boundaries that depend on them. More details will come in the coming weeks on this plan.

This feature is gated by an experimental flag and will only be made available in experimental builds until some future time.
OlimpiaZurek pushed a commit to OlimpiaZurek/react-native that referenced this pull request May 22, 2023
Summary:
This sync includes the following changes:
- **[c28f313e6](facebook/react@c28f313e6 )**: experimental_use(promise) for SSR ([facebook#25214](facebook/react#25214)) //<Andrew Clark>//
- **[d6f9628a8](facebook/react@d6f9628a8 )**: Remove some RSC subset entry points that were removed in the main entry point ([facebook#25209](facebook/react#25209)) //<Sebastian Markbåge>//
- **[a473d08fc](facebook/react@a473d08fc )**: Update to Flow from 0.97 to 0.122 ([facebook#25204](facebook/react#25204)) //<Jan Kassens>//
- **[7028ce745](facebook/react@7028ce745 )**: experimental_use(promise) for Server Components ([facebook#25207](facebook/react#25207)) //<Andrew Clark>//
- **[bfb65681e](facebook/react@bfb65681e )**: experimental_use(context)([facebook#25202](facebook/react#25202)) //<mofeiZ>//
- **[f0efa1164](facebook/react@f0efa1164 )**: [flow] remove custom suppress comment config ([facebook#25170](facebook/react#25170)) //<Jan Kassens>//
- **[2e7f422fe](facebook/react@2e7f422fe )**: Refactor: its type is Container ([facebook#25153](facebook/react#25153)) //<bubucuo>//
- **[2c2d9a1df](facebook/react@2c2d9a1df )**: [eslint-plugin-react-hooks] only allow capitalized component names ([facebook#25162](facebook/react#25162)) //<Jan Kassens>//
- **[36c908a6c](facebook/react@36c908a6c )**: Don't use the Flight terminology in public error messages ([facebook#25166](facebook/react#25166)) //<Sebastian Markbåge>//
- **[8d1b057ec](facebook/react@8d1b057ec )**: [Flight] Minor error handling fixes ([facebook#25151](facebook/react#25151)) //<Sebastian Markbåge>//
- **[9ff738f53](facebook/react@9ff738f53 )**: [devtools][easy] Fix flow type ([facebook#25147](facebook/react#25147)) //<Tianyu Yao>//
- **[0de3ddf56](facebook/react@0de3ddf56 )**: Remove Symbol Polyfill (again) ([facebook#25144](facebook/react#25144)) //<Ricky>//
- **[b36f72235](facebook/react@b36f72235 )**: Remove ReactFiberFlags MountLayoutDev and MountPassiveDev ([facebook#25091](facebook/react#25091)) //<Samuel Susla>//
- **[b6978bc38](facebook/react@b6978bc38 )**: experimental_use(promise) ([facebook#25084](facebook/react#25084)) //<Andrew Clark>//
- **[11ed7010c](facebook/react@11ed7010c )**: [Transition Tracing] onMarkerIncomplete - Tracing Marker/Suspense Boundary Deletions ([facebook#24885](facebook/react#24885)) //<Luna Ruan>//
- **[b79894259](facebook/react@b79894259 )**: [Flight] Add support for Webpack Async Modules ([facebook#25138](facebook/react#25138)) //<Sebastian Markbåge>//
- **[c8b778b7f](facebook/react@c8b778b7f )**: Fix typo: supportsMicrotask -> supportsMicrotasks ([facebook#25142](facebook/react#25142)) //<kwzr>//
- **[d0f396651](facebook/react@d0f396651 )**: Allow functions to be used as module references ([facebook#25137](facebook/react#25137)) //<Sebastian Markbåge>//
- **[38c5d8a03](facebook/react@38c5d8a03 )**: Test the node-register hooks in unit tests ([facebook#25132](facebook/react#25132)) //<Sebastian Markbåge>//
- **[3f70e68ce](facebook/react@3f70e68ce )**: Return closestInstance in `getInspectorDataForViewAtPoint` ([facebook#25118](facebook/react#25118)) //<Tianyu Yao>//
- **[3d443cad7](facebook/react@3d443cad7 )**: Update fixtures/flight to webpack 5 ([facebook#25115](facebook/react#25115)) //<Tim Neutkens>//
- **[5d1ce6513](facebook/react@5d1ce6513 )**: Align StrictMode behaviour with production ([facebook#25049](facebook/react#25049)) //<Samuel Susla>//
- **[9e67e7a31](facebook/react@9e67e7a31 )**: Scaffolding for useMemoCache hook ([facebook#25123](facebook/react#25123)) //<Joseph Savona>//
- **[19e9a4c68](facebook/react@19e9a4c68 )**: Add missing createServerContext for experimental shared subset ([facebook#25114](facebook/react#25114)) //<Jiachi Liu>//
- **[6ef466c68](facebook/react@6ef466c68 )**: make preamble and postamble types explicit and fix typo ([facebook#25102](facebook/react#25102)) //<Josh Story>//
- **[796d31809](facebook/react@796d31809 )**: Implement basic stylesheet Resources for react-dom ([facebook#25060](facebook/react#25060)) //<Josh Story>//
- **[32baab38f](facebook/react@32baab38f )**: [Transition Tracing] Add Tag Field to Marker Instance ([facebook#25085](facebook/react#25085)) //<Luna Ruan>//
- **[8ef3a7c08](facebook/react@8ef3a7c08 )**: Resume immediately pinged fiber without unwinding ([facebook#25074](facebook/react#25074)) //<Andrew Clark>//
- **[7bcc68772](facebook/react@7bcc68772 )**: Remove argument committedLanes from reappearLayoutEffects and recursivelyTraverseReappearLayoutEffects ([facebook#25080](facebook/react#25080)) //<Samuel Susla>//
- **[ca990e9a7](facebook/react@ca990e9a7 )**: Add API to force Scheduler to yield for macrotask ([facebook#25044](facebook/react#25044)) //<Andrew Clark>//
- **[b4204ede6](facebook/react@b4204ede6 )**: Clean up unused Deletion flag ([facebook#24992](facebook/react#24992)) //<Andrew Clark>//
- **[e193be87e](facebook/react@e193be87e )**: [Transition Tracing] Add Offscreen Test ([facebook#25035](facebook/react#25035)) //<Luna Ruan>//
- **[9fcaf88d5](facebook/react@9fcaf88d5 )**: Remove rootContainerInstance from unnecessary places ([facebook#25024](facebook/react#25024)) //<Sebastian Markbåge>//
- **[80f3d8819](facebook/react@80f3d8819 )**: Mount/unmount passive effects when Offscreen visibility changes ([facebook#24977](facebook/react#24977)) //<Andrew Clark>//

Changelog:
[General][Changed] - React Native sync for revisions 4ea064e...c28f313

Reviewed By: rickhanlonii

Differential Revision: D39384898

fbshipit-source-id: 20b080a53851d6dd9d522c8468dd02aab9ba76db
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants