facebook/react
Pull Requests
Succeeded
#20890
[Experiment] Lazily propagate context changes
Succeeded
#25243
[WIP] [Fizz/Float] Float for stylesheet resources
Succeeded
#28668
Warn when using useFormState
Succeeded
#28665
Don't log onRecoverableError if the current commit fail
Succeeded
#28664
Remove errorHydratingContainer
Succeeded
#28663
Dymanic favorSafetyOverHydrationPerf
Succeeded
#28662
Make ART Concurrent if Legacy Mode is disabled
Succeeded
#28661
Update index.js
Succeeded
#28660
Remove orphaned disableJavaScriptURLs reference
Succeeded
#28657
Use the disableLegacyMode where ever we check the ConcurrentMode mode
Failed
#28656
Move ReactDOMLegacy implementation into RootFB
Succeeded
#28655
Add Flag to Favor Hydration Performance over User Safety
Succeeded
#28654
Support suppressHydrationWarning for element-ish text
Succeeded
#28653
Back out #28476 and #28458
Succeeded
#28652
Update error messages
Succeeded
#28650
Remove unmountComponentAtNode outside of legacy mode
Succeeded
#28649
Bump express from 4.18.2 to 4.19.2
Succeeded
#28648
Bump express from 4.17.1 to 4.19.2 in /fixtures/concurrent/time-slicing
Succeeded
#28647
Enable feature flags for v19
Succeeded
#28646
Bump canary versions to v19-canary
Succeeded
#28645
Turn on enableRenderableContext in experimental
Succeeded
#28644
Replace 'var' with 'let' or 'const' for Scheduler.js
Succeeded
#28643
Fix tests on main
Succeeded
#28642
Bump express from 4.17.1 to 4.19.2 in /fixtures/dom
Succeeded
#28641
Make onUncaughtError and onCaughtError Configurable
Succeeded
#28640
Bump express from 4.16.2 to 4.19.2 in /fixtures/packaging/brunch/dev
Succeeded
#28639
Cleanup `alwaysThrottleDisappearingFallbacks` Flag
Succeeded
#28638
Bump express from 4.16.2 to 4.19.2 in /fixtures/expiration
Succeeded
#28637
Bump express from 4.16.2 to 4.19.2 in /fixtures/packaging/brunch/prod
Succeeded
#28636
Bump express from 4.15.4 to 4.19.2 in /fixtures/attribute-behavior
Succeeded
#28635
Add support for preload meadia to ReactDOM
Succeeded
#28634
Bump express from 4.14.0 to 4.19.2 in /fixtures/fiber-debugger
Succeeded
#28633
Switch facebook-www build version to file content hash
Succeeded
#28632
Add useActionState to CHANGELOG-canary.md
Succeeded
#28631
s/form state/action state
Succeeded
#28630
Rh/throttle flag fix
Succeeded
#28629
Fix gating for alwaysThrottleDisappearingFallbacks
Succeeded
#28628
fix[devtools/ci]: split profiling cache test for different react versions and toEqual checker
Succeeded
#28627
[Fiber] Don't Rethrow Errors at the Root
Succeeded
#28625
Add Type: Feature Request to stalebot ignore
Succeeded
#28623
Update README.md
Succeeded
#28621
Bump webpack-dev-middleware from 5.3.3 to 5.3.4
Succeeded
#28620
Choose lazy or value ID based on whether model chunk was emitted
Succeeded
#28618
Bump webpack-dev-middleware from 5.3.3 to 5.3.4 in /fixtures/flight
Succeeded
#28617
Make enableBigIntSupport a dynamic flag for Meta
Succeeded
#28616
Fix test after merge conflict
Succeeded
#28615
[Breaking] Remove disableJavaScriptURLs
Succeeded
#28614
Cleanup enableFormActions flag
Succeeded
#28613
Cleanup enableFloat flag
Succeeded
#28611
[Fizz] Recover from errors thrown by progressive enhancement form generation
Succeeded
#28610
[Flight Reply] Don't allow Symbols to be passed to a reply
Succeeded
#28609
[DO NOT LAND] Allow Previously Seen Client References to be Passed Back to a Reply
Build Activity
Succeeded
#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...
Canceled
#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...
Succeeded
#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...
Succeeded
#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...
Succeeded
#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...
Succeeded
#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...
Succeeded
#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...
Succeeded
#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...
Succeeded
#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...
Canceled
#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...
Succeeded
#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.
Succeeded
#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.
Succeeded
#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...
Canceled
#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...
Succeeded
#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...
Failed
#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 ...
Succeeded
#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 ...
Succeeded
#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 ...
Canceled
#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 ...
Succeeded
#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 ...
Succeeded
#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 ...
Succeeded
#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 ...
Succeeded
#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 ...
Succeeded
#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 ...
Succeeded
#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 ...
Succeeded
#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 ...
Succeeded

facebook/react    #107505

Started duration: 02:14
acdlite opened pull request #20890 to master
Loading Sandboxes...
Loading Packages...
Loading Install Instructions...
Finished!
Loading...