redbox-react

The red box (aka red screen of death) renders an error in this “pretty” format:

Usage

Catch an error and give it to redbox-react. Works with

react-transform-catch-errors (see example or react-transform-boilerplate)
babel-plugin-react-hot & babel-plugin-react-error-catcher (see example)
react-hot-loader (deprecated! see example, relies on changes in unmerged pull request and will not be merged!)

or manually:

constRedBox=require('redbox-react')conste=newError('boom')constbox=<RedBoxerror={e}/>

Here is a more useful, full-fleged example:

/* global __DEV__ */importReactfrom'react'import{render}from'react-dom'importAppfrom'./components/App'constroot=document.getElementById('root')if(__DEV__){constRedBox=require('redbox-react')try{render(<App/>,root)}catch(e){render(<RedBoxerror={e}/>,root)}}else{render(<App/>,root)}

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. You should use this in development only.

Will this catch errors for me?

No. As you can see above, this is only a UI component for rendering errors and their stack traces. It's works great with other solutions, that automate the error catching for you, see the examples.

Optional props

editorScheme[?string] If a filename in the stack trace is local, the component can create the link to open your editor using this scheme eg: subl to create subl://open?url=file:///filename.

useLines[boolean=true] 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.

useColumns[boolean=true] 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.

style[?object] Allows you to override the styles used when rendering the various parts of the component. It will be shallow-merged with the default styles.

If using react-transform-catch-errors you can add these options to your .babelrc through the imports property.

Sourcemaps with Webpack

If using Webpack you can get accurate filenames in the stacktrace by setting the output.devtoolModuleFilenameTemplate settings to /[absolute-resource-path].

It's recommended to set devtool setting to 'eval'.

redbox-react

The red box (aka red screen of death) renders an error in this “pretty” format:

Usage

Catch an error and give it to redbox-react. Works with

react-transform-catch-errors (see example or react-transform-boilerplate)
babel-plugin-react-hot & babel-plugin-react-error-catcher (see example)
react-hot-loader (deprecated! see example, relies on changes in unmerged pull request and will not be merged!)

or manually:

constRedBox=require('redbox-react')conste=newError('boom')constbox=<RedBoxerror={e}/>

Here is a more useful, full-fleged example:

/* global __DEV__ */importReactfrom'react'import{render}from'react-dom'importAppfrom'./components/App'constroot=document.getElementById('root')if(__DEV__){constRedBox=require('redbox-react')try{render(<App/>,root)}catch(e){render(<RedBoxerror={e}/>,root)}}else{render(<App/>,root)}

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. You should use this in development only.

Will this catch errors for me?

No. As you can see above, this is only a UI component for rendering errors and their stack traces. It's works great with other solutions, that automate the error catching for you, see the examples.

Optional props

editorScheme[?string] If a filename in the stack trace is local, the component can create the link to open your editor using this scheme eg: subl to create subl://open?url=file:///filename.

useLines[boolean=true] 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.

useColumns[boolean=true] 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.

style[?object] Allows you to override the styles used when rendering the various parts of the component. It will be shallow-merged with the default styles.

If using react-transform-catch-errors you can add these options to your .babelrc through the imports property.

Sourcemaps with Webpack

If using Webpack you can get accurate filenames in the stacktrace by setting the output.devtoolModuleFilenameTemplate settings to /[absolute-resource-path].

It's recommended to set devtool setting to 'eval'.

redbox-react

The red box (aka red screen of death) renders an error in this “pretty” format:

Usage

Catch an error and give it to redbox-react. Works with

react-transform-catch-errors (see example or react-transform-boilerplate)
babel-plugin-react-hot & babel-plugin-react-error-catcher (see example)
react-hot-loader (deprecated! see example, relies on changes in unmerged pull request and will not be merged!)

or manually:

constRedBox=require('redbox-react')conste=newError('boom')constbox=<RedBoxerror={e}/>

Here is a more useful, full-fleged example:

/* global __DEV__ */importReactfrom'react'import{render}from'react-dom'importAppfrom'./components/App'constroot=document.getElementById('root')if(__DEV__){constRedBox=require('redbox-react')try{render(<App/>,root)}catch(e){render(<RedBoxerror={e}/>,root)}}else{render(<App/>,root)}

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. You should use this in development only.

Will this catch errors for me?

No. As you can see above, this is only a UI component for rendering errors and their stack traces. It's works great with other solutions, that automate the error catching for you, see the examples.

Optional props

editorScheme[?string] If a filename in the stack trace is local, the component can create the link to open your editor using this scheme eg: subl to create subl://open?url=file:///filename.

useLines[boolean=true] 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.

useColumns[boolean=true] 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.

style[?object] Allows you to override the styles used when rendering the various parts of the component. It will be shallow-merged with the default styles.

If using react-transform-catch-errors you can add these options to your .babelrc through the imports property.

Sourcemaps with Webpack

If using Webpack you can get accurate filenames in the stacktrace by setting the output.devtoolModuleFilenameTemplate settings to /[absolute-resource-path].

It's recommended to set devtool setting to 'eval'.

redbox-react

The red box (aka red screen of death) renders an error in this “pretty” format:

Usage

Catch an error and give it to redbox-react. Works with

react-transform-catch-errors (see example or react-transform-boilerplate)
babel-plugin-react-hot & babel-plugin-react-error-catcher (see example)
react-hot-loader (deprecated! see example, relies on changes in unmerged pull request and will not be merged!)

or manually:

constRedBox=require('redbox-react')conste=newError('boom')constbox=<RedBoxerror={e}/>

Here is a more useful, full-fleged example:

/* global __DEV__ */importReactfrom'react'import{render}from'react-dom'importAppfrom'./components/App'constroot=document.getElementById('root')if(__DEV__){constRedBox=require('redbox-react')try{render(<App/>,root)}catch(e){render(<RedBoxerror={e}/>,root)}}else{render(<App/>,root)}

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. You should use this in development only.

Will this catch errors for me?

No. As you can see above, this is only a UI component for rendering errors and their stack traces. It's works great with other solutions, that automate the error catching for you, see the examples.

Optional props

editorScheme[?string] If a filename in the stack trace is local, the component can create the link to open your editor using this scheme eg: subl to create subl://open?url=file:///filename.

useLines[boolean=true] 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.

useColumns[boolean=true] 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.

style[?object] Allows you to override the styles used when rendering the various parts of the component. It will be shallow-merged with the default styles.

If using react-transform-catch-errors you can add these options to your .babelrc through the imports property.

Sourcemaps with Webpack

If using Webpack you can get accurate filenames in the stacktrace by setting the output.devtoolModuleFilenameTemplate settings to /[absolute-resource-path].

It's recommended to set devtool setting to 'eval'.

redbox-react

The red box (aka red screen of death) renders an error in this “pretty” format:

Usage

Catch an error and give it to redbox-react. Works with

react-transform-catch-errors (see example or react-transform-boilerplate)
babel-plugin-react-hot & babel-plugin-react-error-catcher (see example)
react-hot-loader (deprecated! see example, relies on changes in unmerged pull request and will not be merged!)

or manually:

constRedBox=require('redbox-react')conste=newError('boom')constbox=<RedBoxerror={e}/>

Here is a more useful, full-fleged example:

/* global __DEV__ */importReactfrom'react'import{render}from'react-dom'importAppfrom'./components/App'constroot=document.getElementById('root')if(__DEV__){constRedBox=require('redbox-react')try{render(<App/>,root)}catch(e){render(<RedBoxerror={e}/>,root)}}else{render(<App/>,root)}

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. You should use this in development only.

Will this catch errors for me?

No. As you can see above, this is only a UI component for rendering errors and their stack traces. It's works great with other solutions, that automate the error catching for you, see the examples.

Optional props

editorScheme[?string] If a filename in the stack trace is local, the component can create the link to open your editor using this scheme eg: subl to create subl://open?url=file:///filename.

useLines[boolean=true] 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.

useColumns[boolean=true] 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.

style[?object] Allows you to override the styles used when rendering the various parts of the component. It will be shallow-merged with the default styles.

If using react-transform-catch-errors you can add these options to your .babelrc through the imports property.

Sourcemaps with Webpack

If using Webpack you can get accurate filenames in the stacktrace by setting the output.devtoolModuleFilenameTemplate settings to /[absolute-resource-path].

It's recommended to set devtool setting to 'eval'.

redbox-react

The red box (aka red screen of death) renders an error in this “pretty” format:

Usage

Catch an error and give it to redbox-react. Works with

react-transform-catch-errors (see example or react-transform-boilerplate)
babel-plugin-react-hot & babel-plugin-react-error-catcher (see example)
react-hot-loader (deprecated! see example, relies on changes in unmerged pull request and will not be merged!)

or manually:

constRedBox=require('redbox-react')conste=newError('boom')constbox=<RedBoxerror={e}/>

Here is a more useful, full-fleged example:

/* global __DEV__ */importReactfrom'react'import{render}from'react-dom'importAppfrom'./components/App'constroot=document.getElementById('root')if(__DEV__){constRedBox=require('redbox-react')try{render(<App/>,root)}catch(e){render(<RedBoxerror={e}/>,root)}}else{render(<App/>,root)}

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. You should use this in development only.

Will this catch errors for me?

No. As you can see above, this is only a UI component for rendering errors and their stack traces. It's works great with other solutions, that automate the error catching for you, see the examples.

Optional props

editorScheme[?string] If a filename in the stack trace is local, the component can create the link to open your editor using this scheme eg: subl to create subl://open?url=file:///filename.

useLines[boolean=true] 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.

useColumns[boolean=true] 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.

style[?object] Allows you to override the styles used when rendering the various parts of the component. It will be shallow-merged with the default styles.

If using react-transform-catch-errors you can add these options to your .babelrc through the imports property.

Sourcemaps with Webpack

If using Webpack you can get accurate filenames in the stacktrace by setting the output.devtoolModuleFilenameTemplate settings to /[absolute-resource-path].

It's recommended to set devtool setting to 'eval'.

redbox-react

The red box (aka red screen of death) renders an error in this “pretty” format:

Usage

Catch an error and give it to redbox-react. Works with

react-transform-catch-errors (see example or react-transform-boilerplate)
babel-plugin-react-hot & babel-plugin-react-error-catcher (see example)
react-hot-loader (deprecated! see example, relies on changes in unmerged pull request and will not be merged!)

or manually:

constRedBox=require('redbox-react')conste=newError('boom')constbox=<RedBoxerror={e}/>

Here is a more useful, full-fleged example:

/* global __DEV__ */importReactfrom'react'import{render}from'react-dom'importAppfrom'./components/App'constroot=document.getElementById('root')if(__DEV__){constRedBox=require('redbox-react')try{render(<App/>,root)}catch(e){render(<RedBoxerror={e}/>,root)}}else{render(<App/>,root)}

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. You should use this in development only.

Will this catch errors for me?

No. As you can see above, this is only a UI component for rendering errors and their stack traces. It's works great with other solutions, that automate the error catching for you, see the examples.

Optional props

editorScheme[?string] If a filename in the stack trace is local, the component can create the link to open your editor using this scheme eg: subl to create subl://open?url=file:///filename.

useLines[boolean=true] 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.

useColumns[boolean=true] 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.

style[?object] Allows you to override the styles used when rendering the various parts of the component. It will be shallow-merged with the default styles.

If using react-transform-catch-errors you can add these options to your .babelrc through the imports property.

Sourcemaps with Webpack

If using Webpack you can get accurate filenames in the stacktrace by setting the output.devtoolModuleFilenameTemplate settings to /[absolute-resource-path].

It's recommended to set devtool setting to 'eval'.

redbox-react

The red box (aka red screen of death) renders an error in this “pretty” format:

Usage

Catch an error and give it to redbox-react. Works with

react-transform-catch-errors (see example or react-transform-boilerplate)
babel-plugin-react-hot & babel-plugin-react-error-catcher (see example)
react-hot-loader (deprecated! see example, relies on changes in unmerged pull request and will not be merged!)

or manually:

constRedBox=require('redbox-react')conste=newError('boom')constbox=<RedBoxerror={e}/>

Here is a more useful, full-fleged example:

/* global __DEV__ */importReactfrom'react'import{render}from'react-dom'importAppfrom'./components/App'constroot=document.getElementById('root')if(__DEV__){constRedBox=require('redbox-react')try{render(<App/>,root)}catch(e){render(<RedBoxerror={e}/>,root)}}else{render(<App/>,root)}

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. You should use this in development only.

Will this catch errors for me?

No. As you can see above, this is only a UI component for rendering errors and their stack traces. It's works great with other solutions, that automate the error catching for you, see the examples.

Optional props

editorScheme[?string] If a filename in the stack trace is local, the component can create the link to open your editor using this scheme eg: subl to create subl://open?url=file:///filename.

useLines[boolean=true] 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.

useColumns[boolean=true] 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.

style[?object] Allows you to override the styles used when rendering the various parts of the component. It will be shallow-merged with the default styles.

If using react-transform-catch-errors you can add these options to your .babelrc through the imports property.

Sourcemaps with Webpack

If using Webpack you can get accurate filenames in the stacktrace by setting the output.devtoolModuleFilenameTemplate settings to /[absolute-resource-path].

It's recommended to set devtool setting to 'eval'.

Name		Name	Last commit message	Last commit date
examples		examples
src		src
tests		tests
.babelrc		.babelrc
.csslintrc		.csslintrc
.gitignore		.gitignore
.travis.yml		.travis.yml
CHANGELOG.md		CHANGELOG.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
LICENSE.md		LICENSE.md
README.md		README.md
make-webpack-config.js		make-webpack-config.js
package.json		package.json
webpack.config.js		webpack.config.js
webpack.config.prod.js		webpack.config.prod.js

Name		Name	Last commit message	Last commit date
examples		examples
src		src
tests		tests
.babelrc		.babelrc
.csslintrc		.csslintrc
.gitignore		.gitignore
.travis.yml		.travis.yml
CHANGELOG.md		CHANGELOG.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
LICENSE.md		LICENSE.md
README.md		README.md
make-webpack-config.js		make-webpack-config.js
package.json		package.json
webpack.config.js		webpack.config.js
webpack.config.prod.js		webpack.config.prod.js

Name		Name	Last commit message	Last commit date
examples		examples
src		src
tests		tests
.babelrc		.babelrc
.csslintrc		.csslintrc
.gitignore		.gitignore
.travis.yml		.travis.yml
CHANGELOG.md		CHANGELOG.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
LICENSE.md		LICENSE.md
README.md		README.md
make-webpack-config.js		make-webpack-config.js
package.json		package.json
webpack.config.js		webpack.config.js
webpack.config.prod.js		webpack.config.prod.js

Name		Name	Last commit message	Last commit date
examples		examples
src		src
tests		tests
.babelrc		.babelrc
.csslintrc		.csslintrc
.gitignore		.gitignore
.travis.yml		.travis.yml
CHANGELOG.md		CHANGELOG.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
LICENSE.md		LICENSE.md
README.md		README.md
make-webpack-config.js		make-webpack-config.js
package.json		package.json
webpack.config.js		webpack.config.js
webpack.config.prod.js		webpack.config.prod.js

Name		Name	Last commit message	Last commit date
examples		examples
src		src
tests		tests
.babelrc		.babelrc
.csslintrc		.csslintrc
.gitignore		.gitignore
.travis.yml		.travis.yml
CHANGELOG.md		CHANGELOG.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
LICENSE.md		LICENSE.md
README.md		README.md
make-webpack-config.js		make-webpack-config.js
package.json		package.json
webpack.config.js		webpack.config.js
webpack.config.prod.js		webpack.config.prod.js

Latest commit

History

Folders and files

Repository files navigation

redbox-react

Usage

What is this good for?

Will this catch errors for me?

Optional props

Sourcemaps with Webpack

About

Resources

Code of conduct

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

redbox-react

Usage

What is this good for?

Will this catch errors for me?

Optional props

Sourcemaps with Webpack

About

Resources

Code of conduct

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

redbox-react

Usage

What is this good for?

Will this catch errors for me?

Optional props

Sourcemaps with Webpack

About

Resources

Code of conduct

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

redbox-react

Usage

What is this good for?

Will this catch errors for me?

Optional props

Sourcemaps with Webpack

About

Resources

Code of conduct

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages