-
Notifications
You must be signed in to change notification settings - Fork 49k
Update error minification script to support Error call expressions #22428
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -287,12 +287,10 @@ | |
"288": "It is not supported to run the profiling version of a renderer (for example, `react-dom/profiling`) without also replacing the `schedule/tracing` module with `schedule/tracing-profiling`. Your bundler might have a setting for aliasing both modules. Learn more at https://reactjs.org/link/profiling", | ||
"289": "Function components cannot have refs.", | ||
"290": "Element ref was specified as a string (%s) but no owner was set. This could happen for one of the following reasons:\n1. You may be adding a ref to a function component\n2. You may be adding a ref to a component that was not created inside a component's render method\n3. You have multiple copies of React loaded\nSee https://reactjs.org/link/refs-must-have-owner for more information.", | ||
"291": "Log of yielded values is not empty. Call expect(Scheduler).toHaveYielded(...) first.", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. See https://github.com/facebook/react/pull/22428/files#r716105083. Since this message was never part of a public bundle we can remove it. |
||
"292": "The matcher `toHaveYielded` expects an instance of React Test Renderer.\n\nTry: expect(Scheduler).toHaveYielded(expectedYields)", | ||
"293": "Context can only be read while React is rendering, e.g. inside the render method or getDerivedStateFromProps.", | ||
"294": "ReactDOMServer does not yet support Suspense.", | ||
"295": "ReactDOMServer does not yet support lazy-loaded components.", | ||
"296": "Log of yielded values is not empty. Call expect(ReactTestRenderer).unstable_toHaveYielded(...) first.", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same here |
||
"297": "The matcher `unstable_toHaveYielded` expects an instance of React Test Renderer.\n\nTry: expect(ReactTestRenderer).unstable_toHaveYielded(expectedYields)", | ||
"298": "Hooks can only be called inside the body of a function component.", | ||
"299": "createRoot(...): Target container is not a DOM element.", | ||
|
@@ -397,5 +395,6 @@ | |
"406": "act(...) is not supported in production builds of React.", | ||
"407": "Missing getServerSnapshot, which is required for server-rendered content. Will revert to client rendering.", | ||
"408": "Missing getServerSnapshot, which is required for server-rendered content.", | ||
"409": "Cannot update an unmounted root." | ||
"409": "Cannot update an unmounted root.", | ||
"410": "%s suspended while rendering, but no fallback UI was specified.\n\nAdd a <Suspense fallback=...> component higher in the tree to provide a loading indicator or placeholder to display." | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noticed this was being minified in jest-react but that's an internal module so there's no reason to. The extract-errors script must have picked this up at some point. Since it's not part of a public bundle we don't have to minify it.