Pull Requests
#20890
[Experiment] Lazily propagate context changes
#25243
[WIP] [Fizz/Float] Float for stylesheet resources
#28668
Warn when using useFormState
#28665
Don't log onRecoverableError if the current commit fail
#28664
Remove errorHydratingContainer
#28663
Dymanic favorSafetyOverHydrationPerf
#28662
Make ART Concurrent if Legacy Mode is disabled
#28661
Update index.js
#28660
Remove orphaned disableJavaScriptURLs reference
#28657
Use the disableLegacyMode where ever we check the ConcurrentMode mode
#28656
Move ReactDOMLegacy implementation into RootFB
#28655
Add Flag to Favor Hydration Performance over User Safety
#28654
Support suppressHydrationWarning for element-ish text
#28653
Back out #28476 and #28458
#28652
Update error messages
#28650
Remove unmountComponentAtNode outside of legacy mode
#28649
Bump express from 4.18.2 to 4.19.2
#28648
Bump express from 4.17.1 to 4.19.2 in /fixtures/concurrent/time-slicing
#28647
Enable feature flags for v19
#28646
Bump canary versions to v19-canary
#28645
Turn on enableRenderableContext in experimental
#28644
Replace 'var' with 'let' or 'const' for Scheduler.js
#28643
Fix tests on main
#28642
Bump express from 4.17.1 to 4.19.2 in /fixtures/dom
#28641
Make onUncaughtError and onCaughtError Configurable
#28640
Bump express from 4.16.2 to 4.19.2 in /fixtures/packaging/brunch/dev
#28639
Cleanup `alwaysThrottleDisappearingFallbacks` Flag
#28638
Bump express from 4.16.2 to 4.19.2 in /fixtures/expiration
#28637
Bump express from 4.16.2 to 4.19.2 in /fixtures/packaging/brunch/prod
#28636
Bump express from 4.15.4 to 4.19.2 in /fixtures/attribute-behavior
#28635
Add support for preload meadia to ReactDOM
#28634
Bump express from 4.14.0 to 4.19.2 in /fixtures/fiber-debugger
#28633
Switch facebook-www build version to file content hash
#28632
Add useActionState to CHANGELOG-canary.md
#28631
s/form state/action state
#28630
Rh/throttle flag fix
#28629
Fix gating for alwaysThrottleDisappearingFallbacks
#28628
fix[devtools/ci]: split profiling cache test for different react versions and toEqual checker
#28627
[Fiber] Don't Rethrow Errors at the Root
#28625
Add Type: Feature Request to stalebot ignore
#28623
Update README.md
#28621
Bump webpack-dev-middleware from 5.3.3 to 5.3.4
#28620
Choose lazy or value ID based on whether model chunk was emitted
#28618
Bump webpack-dev-middleware from 5.3.3 to 5.3.4 in /fixtures/flight
#28617
Make enableBigIntSupport a dynamic flag for Meta
#28616
Fix test after merge conflict
#28615
[Breaking] Remove disableJavaScriptURLs
#28614
Cleanup enableFormActions flag
#28613
Cleanup enableFloat flag
#28611
[Fizz] Recover from errors thrown by progressive enhancement form generation
#28610
[Flight Reply] Don't allow Symbols to be passed to a reply
#28609
[DO NOT LAND] Allow Previously Seen Client References to be Passed Back to a Reply
Build Activity
#107505
Mark trees that need propagation in readContext
Instead of storing matched context consumers in a Set, we can mark
when a consumer receives an update inside `readContext`.
I hesistated to put anything in this function because it's such a hot
path, bu...
#107504
Move context comparison to consumer
In the lazy context implementation, not all context changes are
propagated from the provider, so we can't rely on the propagation alone
to mark the consumer as dirty. The consumer needs to compare to the
previous va...
#106409
Mark trees that need propagation in readContext
Instead of storing matched context consumers in a Set, we can mark
when a consumer receives an update inside `readContext`.
I hesistated to put anything in this function because it's such a hot
path, bu...
#106064
Mark trees that need propagation in readContext
Instead of storing matched context consumers in a Set, we can mark
when a consumer receives an update inside `readContext`.
I hesistated to put anything in this function because it's such a hot
path, bu...
#105821
Mark trees that need propagation in readContext
Instead of storing matched context consumers in a Set, we can mark
when a consumer receives an update inside `readContext`.
I hesistated to put anything in this function because it's such a hot
path, bu...
#105806
Mark trees that need propagation in readContext
Instead of storing matched context consumers in a Set, we can mark
when a consumer receives an update inside `readContext`.
I hesistated to put anything in this function because it's such a hot
path, bu...
#105796
Stop propagating at nearest dependency match
Because we now propagate all context providers in a single traversal, we
can defer context propagation to a subtree without losing information
about which context providers we're deferring — it's all of the...
#105793
Stop propagating at nearest dependency match
Because we now propagate all context providers in a single traversal, we
can defer context propagation to a subtree without losing information
about which context providers we're deferring — it's all of the...
#105792
Stop propagating at nearest dependency match
Because we now propagate all context providers in a single traversal, we
can defer context propagation to a subtree without losing information
about which context providers we're deferring — it's all of the...
#105791
Stop propagating at nearest dependency match
Because we now propagate all context providers in a single traversal, we
can defer context propagation to a subtree without losing information
about which context providers we're deferring — it's all of the...
#105560
Don't check parent deps if child already matched
Because we traverse the whole tree regardless, we can avoid looking
for changes in a parent node if a child node already matched.
#105559
Don't check parent deps if child already matched
Because we traverse the whole tree regardless, we can avoid looking
for changes in a parent node if a child node already matched.
#105549
Propagate all contexts in single pass
Instead of propagating the tree once per changed context, we can check
all the contexts in a single propagation. This inverts the two loops so
that the faster loop (O(numberOfContexts)) is inside the more expensiv...
#105548
Propagate all contexts in single pass
Instead of propagating the tree once per changed context, we can check
all the contexts in a single propagation. This inverts the two loops so
that the faster loop (O(numberOfContexts)) is inside the more expensiv...
#105532
[Experiment] Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper is...
#105441
Experiment: Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper
is ...
#105232
Experiment: Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper
is ...
#105228
Experiment: Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper
is ...
#105227
Experiment: Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper
is ...
#105221
Experiment: Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper
is ...
#105220
Experiment: Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper
is ...
#105217
Experiment: Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper
is ...
#105215
Experiment: Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper
is ...
#105214
Experiment: Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper
is ...
#105211
Experiment: Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper
is ...
#105210
Experiment: Lazily propagate context changes
When a context provider changes, we scan the tree for matching consumers
and mark them as dirty so that we know they have pending work. This
prevents us from bailing out if, say, an intermediate wrapper
is ...
facebook/react #107505
Loading Sandboxes...
Loading Packages...
Loading Install Instructions...
Finished!