A crash in the interface now reports itself instead of leaving a blank screen.
What's wrong with this entry?
The component that catches crashes in the UI previously just recorded that an error happened and rendered nothing. It now reports the error and calls an optional onError handler, so a failed render surfaces rather than disappearing.
componentDidCatch
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.228
API rejections are classified from a structured marker instead of prose alone
Both mention error
-
v2.1.228
Oversized media in a request is now its own rejection class
Both mention error
-
v2.1.234
Empty or malformed API responses now report what actually answered
Both mention error