Pull Requests
#20890
[Experiment] Lazily propagate context changes
#21122
Fix: flushSync changes priority inside effect
#28952
move from `importAssertions` to `importAttributes`
#28951
Test StrictEffects in react-dom
#28950
Update config.yml
#28949
Gaurav added a message
#28945
pranav added a message
#28944
chore: export cjs/umd as v17
#28942
Fix useActionState PendingState Type
#28940
Added a hyperlink to Node
#28939
Import correct prod version of jsx-dev-runtime for react-server
#28937
Fixed it: Update CODE_OF_CONDUCT.md
#28936
feat(badge): Add JSDelivr badge
#28934
fix(hydrate): to check and add validations for type check of argument…
#28932
Add changelog for 18.3.1
#28930
Configure JSX Feature Flags as Dynamic (Meta)
#28929
Add changelog for 18.3 and 18.3.1
#28927
[Not for merge] 18.3.1 Release
#28925
Update Changelog for 18.3.0
#28921
fix: react server condition for `react/jsx-dev-runtime`
#28920
Update made
#28919
[react-dom] Provide a way to silence devtools recommendation
#28916
Export `React.act` from 18.3
#28912
(Land #28798) Move Current Owner (and Cache) to an Async Dispatcher
#28911
Go back to shared refs instance object
#28910
Support ref cleanup function for imperative handle refs
#28909
Reconciler: Change `commitUpdate` signature to account for unused `updatePayload` parameter
#28907
[Flight][Fizz] tasks that ping in a microtask should render synchronously
#28906
Update README.md
#28905
Update canary channel label to "beta"
#28904
warn -> error for Test Renderer deprecation
#28902
Update App.test.js
#28901
fix: export `jsx-runtime.react-server.js` as `react/jsx-dev-runtime`
#28900
[Flight][Fizz] schedule flushing independently from performing work
#28899
Create short link for jsx warning
#28896
Remove automatic fetch `cache` instrumentation
#28895
Add ref callback test for cleanup fn vs null call
#28894
[Flight][Fizz] ping work within current task
#28893
[Flight Reply] Encode ReadableStream and AsyncIterables
#28892
Install ESLint v9
#28891
Cleanup `replayFailedUnitOfWorkWithInvokeGuardedCallback`and `enableProfilerNestedUpdateScheduledHook`
#28890
Fix readme errors
#28889
Update README.md
#28888
ljust for example
#28887
Use undici polyfill for tests in old Node versions
#28883
Remove warning for ref cleanup function
#28881
Don't minify symbols in production builds
#28880
Build react-reconciler for FB builds
#28879
Unrevert "Support writing to this.refs from userspace"
#28878
[Experiment] Reuse memo cache after interruption
#28877
Revert "Support writing to this.refs from userspace"
#28875
convert circleci workflow devtools_regression_tests to github actions
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 #105217
Loading Sandboxes...
Loading Packages...
Loading Install Instructions...
Finished!