Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

redbox-react

Package Overview
Dependencies
Maintainers
2
Versions
34
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

redbox-react

A redbox (rsod) component to display your errors.

  • 1.6.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
65K
decreased by-31.81%
Maintainers
2
Weekly downloads
 
Created
Source

redbox-react

Build Status semantic-release

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

red screen of death

Usage

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

or manually:

import RedBox from 'redbox-react'

const e = new Error('boom')
const box = <RedBox error={e} />

Here is a more useful, full-fleged example:

/* global __DEV__ */
import React from 'react'
import { render } from 'react-dom'
import App from './components/App'

const root = document.getElementById('root')

if (__DEV__) {
  const RedBox = require('redbox-react').default
  try {
    render(<App />, root)
  } catch (e) {
    render(<RedBox error={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.

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.

Optional Props

The RedBox component takes a couple of props that you can use to customize its behaviour:

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.
  • or vscode to create vscode://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 you’re using react-transform-catch-errors you can add these options to your .babelrc through the imports property.

Sourcemaps With Webpack

If you’re 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 the devtool setting to 'eval'.

Keywords

FAQs

Package last updated on 26 Apr 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc