The red box (aka red screen of death) renders an error in this “pretty” format:
Catch an error and give it to
redbox-react. Works great with
- ⚠️ ️ based on
3.0.0-beta.2! This depends on
ErrorBoundarieswhich will likely not land in react! You should probably not use this before 3.0.0 comes out.
- ⚠️ ️ based on
const e = 'boom'const box = <RedBox error=e />
Here is a more useful, full-fleged example:
/* global __DEV__ */const root = documentif __DEV__const RedBox = defaulttrycatch eelse
What Is This Good For?
An error that's only in the console is only half the fun. Now you can use all the wasted space where your app would be if it didn’t crash to display the error that made it crash.
Please use this in development only.
Will this catch errors for me?
No. This is only a UI component for rendering errors and their stack traces. It is intended to be used with with other existing solutions that automate the error catching for you. See the list at the top of this document or take a look at the examples.
RedBox component takes a couple of props that you can use to
customize its behaviour:
If a filename in the stack trace is local, the component can create the link to open your editor using this scheme eg:
Line numbers in the stack trace may be unreliable depending on the type of sourcemaps. You can choose to not display them with this flag.
Column numbers in the stack trace may be unreliable depending on the type of sourcemaps. You can choose to not display them with this flag.
Allows you to override the styles used when rendering the various parts of the component. It will be shallow-merged with the default styles.
Sourcemaps With Webpack
If you’re using Webpack you can get
accurate filenames in the stacktrace by setting the
output.devtoolModuleFilenameTemplate settings to
It's recommended to set the
devtool setting to