Pull Requests
#22516
Output FIXME during build for unminified errors
#25071
all better
#27527
Bump undici from 5.22.1 to 5.26.2 in /fixtures/flight-esm
#23051
fixed:webComponent can receive child elements
#29046
fix(eslint-plugin-react-hooks): "additionalHooks" docs are misleading
#29044
Set the current fiber to the source of the error during error reporting
#29043
[Flight] Error if a legacy React Element is attempted to be rendered
#29041
Clean up the enableEarlyReturnForPropDiffing experiment
#29039
Add `useNativeProcessing()` flag for Fabric ViewConfigs
#29038
Unify ReactFiberCurrentOwner and ReactCurrentFiber
#29035
[Flight] Enable Binary and ReadableStreams in Stable
#29032
Track Stack of JSX Calls
#29030
ADD A CODE COMMENT
#29028
Use `FormData` `submitter` parameter
#29027
Remove 2 no longer existing files from inlinedHostConfig
#29026
Upgrade jest and jsdom
#29025
Facebook: merge react index.classic.fb and index.modern.fb
#29023
fix[react-devtools/InspectedElementView.css]: dont draw bottom border for empty badge list
#29022
React DevTools 5.1.0 -> 5.2.0
#29019
Support useFormStatus in progressively-enhanced forms
#29016
fix[react-devtools/ci]: fix configurations for e2e testing
#29015
Clean up fastAddProperties and make it more correct
#29014
feat[react-devtools]: display forget badge for components in profiling session
#29013
a
#29010
[Flight Reply] Encode Objects Returned to the Client by Reference
#29009
Check if we ever test without consoleManagedByDevToolsDuringStrictMode
#29008
Stop using Scheduler.log to test double invocations
#29007
Dim `console` calls on additional Effect invocations due to `StrictMode`
#29006
Allow specifying timeout in tests via third argument
#29004
"TypeError: Cannot read property 'setState' of null" when using React.lazy
#29003
Add FB build for ReactReconcilerConstants
#29002
Update getComments.js
#29001
[Flight] Test deduplication with streaming server components
#28997
[Flight Reply] Dedupe Objects and Support Cyclic References
#28996
[Flight] Encode references to existing objects by property path
#28993
refactored shebangs
#28991
Sanitize key
#28990
Setup Wave 2 of Feature Flags for React Native
#28989
Update `compiled-rn` destination paths to `vendor/react`
#28988
[Flight Reply] Resolve outlined models async in Reply just like in Flight Client
#28987
[Fizz] Fallback to client replaying actions if we're trying to serialize a Blob
#28986
[Flight Reply] Encode binary streams as a single collapsed Blob
#28982
fix[react-devtools]: add backwards compat with legacy element type symbol
#28980
Repro for string ref + enableRefAsProp unstable props
#28979
Bundle config: Rename `global` to `hasteFileName` in bundle config
#28978
Bundle config: inline internal hook wrapper
#28977
Enable Wave 1 of Feature Flags for React Native
#28976
Devtools: Fix build-for-devtools
#28975
Devtools: Streamline getting extension from branch
#28974
DevTools: Fix inspecting components with multiple reads of the same Context in React 17
#28973
[DevTools] Expose "view source" options to Fusebox integration
#28972
[DevTools] Enable inspected element context menu in Fusebox
#28970
[DevTools] Check in `frontend.d.ts` for react-devtools-fusebox, include in build output
#28969
Introduce a faster version of the addProperties function
Build Activity
#183729
Replace old extract-errors script with new one
Deletes the old extract-errors in favor of extract-errors2
#176927
Replace old extract-errors script with new one
Deletes the old extract-errors in favor of extract-errors2
#176680
Replace old extract-errors script with new one
Deletes the old extract-errors in favor of extract-errors2
#176678
Replace old extract-errors script with new one
Deletes the old extract-errors in favor of extract-errors2
#176676
Replace old extract-errors script with new one
Deletes the old extract-errors in favor of extract-errors2
#176665
Replace old extract-errors script with new one
Deletes the old extract-errors in favor of extract-errors2
#176597
Disable error minification in more bundles
Not worth it because the number of errors does not outweight the size
of the formatProdErrorMessage runtime.
#176589
Disable error minification in more bundles
Not worth it because the number of errors does not outweight the size
of the formatProdErrorMessage runtime.
#176560
Disable error minification in more bundles
Not worth it because the number of errors does not outweight the size
of the formatProdErrorMessage runtime.
#176552
Disable error minification in more bundles
Not worth it because the number of errors does not outweight the size
of the formatProdErrorMessage runtime.
#176551
Disable error minification in react-noop-renderer
These aren't user facing, so there's no reason to add these messages
to the error code map.
#176548
Update codes.json with extract-errors2
These new messages are ones that we opted out of minifying with ESLint,
but appear in builds are configured to have minified errors in our
Rollup config. We probably don't want to land all of these.
#176546
Alternate extract-errors that scrapes artifacts
The build script outputs a special FIXME comment when it fails to minify
an error message. CI will detect these comments and fail the workflow.
The comments also include the expected error message. So I...
#176538
Alternate extract-errors that scrapes artifacts
The build script outputs a special FIXME comment when it fails to minify
an error message. CI will detect these comments and fail the workflow.
The comments also include the expected error message. So I...
#176537
Alternate extract-errors that scrapes artifacts
The build script outputs a special FIXME comment when it fails to minify
an error message. CI will detect these comments and fail the workflow.
The comments also include the expected error message. So I...
#176534
Alternate extract-errors that scrapes artifacts
The build script outputs a special FIXME comment when it fails to minify
an error message. CI will detect these comments and fail the workflow.
The comments also include the expected error message. So I...
#176522
Add ! to FIXME comment so Closure doesn't strip it
Don't love this solution because Closure could change this heuristic,
or we could switch to a differnt compiler that doesn't support it. But
it works.
Could add a bundle that contains an unminified e...
#176521
Don't run error transform in development
We used to run the error transform in both production and development,
because in development it was used to convert `invariant` calls into
throw statements.
Now that don't use `invariant` anymore, we only hav...
#176515
Don't run error transform in development
We used to run the error transform in both production and development,
because in development it was used to convert `invariant` calls into
throw statements.
Now that don't use `invariant` anymore, we only hav...
#176511
Don't run error transform in development
We used to run the error transform in both production and development,
because in development it was used to convert `invariant` calls into
throw statements.
Now that don't use `invariant` anymore, we only hav...
#176507
Add ! to FIXME comment so Closure doesn't strip it
Don't love this solution because Closure could change this heuristic,
or we could switch to a differnt compiler that doesn't support it. But
it works.
Could add a bundle that contains an unminified e...
#176503
Don't run error transform in development
We used to run the error transform in both production and development,
because in development it was used to convert `invariant` calls into
throw statements.
Now that don't use `invariant` anymore, we only hav...
#176500
Don't run error transform in development
We used to run the error transform in both production and development,
because in development it was used to convert `invariant` calls into
throw statements.
Now that don't use `invariant` anymore, we only hav...
#176498
Don't run error transform in development
We used to run the error transform in both production and development,
because in development it was used to convert `invariant` calls into
throw statements.
Now that don't use `invariant` anymore, we only hav...
#176496
Don't run error transform in development
We used to run the error transform in both production and development,
because in development it was used to convert `invariant` calls into
throw statements.
Now that don't use `invariant` anymore, we only hav...
#176492
Output FIXME during build for unminified errors
The invariant Babel transform used to output a FIXME comment if it
could not find a matching error code. This could happen if there were
a configuration mistake that caused an unminified message to
slip ...
#176491
Output FIXME during build for unminified errors
The invariant Babel transform used to output a FIXME comment if it
could not find a matching error code. This could happen if there were
a configuration mistake that caused an unminified message to
slip ...
facebook/react    #176496
Loading Sandboxes...
Loading Packages...
Loading Install Instructions...
Finished!