Skip to content

Releases: gaearon/react-transform-catch-errors

v1.0.2

02 Feb 17:22
Compare
Choose a tag to compare
  • Removes unnecessary files from the npm package (72b0976)

v1.0.1

25 Dec 16:03
Compare
Choose a tag to compare
  • Displays the offending call stack more prominently by rethrowing on the next tick instead of using console.error (#10, #12, 92057fd)

v1.0.0

19 Sep 16:55
Compare
Choose a tag to compare

Breaking Change

The transform no longer takes precautions to become a no-op in production environment. It is now your responsibility to only enable it in development environment.

Make sure to wrap your React Transform configuration into env.development inside .babelrc:

{
  "stage": 0,
  "env": {

    // only enable it when process.env.NODE_ENV is not 'production'

    "development": {
      "plugins": ["react-transform"],
      "extra": {
        "react-transform": [{
          "target": "react-transform-catch-errors",
          "imports": ["react", "redbox-react"]
        }]
      }
    }
  }
}

Then make sure you're running Babel with NODE_ENV=production in the production.

v0.2.0

17 Sep 18:35
Compare
Choose a tag to compare
  • Pass arbitrary configuration to the error reporter by specifying a module as a third import. This module is expected to export an object which will be spread over in ErrorReporter props.

v0.1.3

15 Sep 16:36
Compare
Choose a tag to compare
  • Pass filename to the error reporter component. (#5)

v0.1.2

12 Sep 13:11
Compare
Choose a tag to compare
  • Don't trigger react-native error handler (#4)

v0.1.1

03 Sep 01:29
Compare
Choose a tag to compare
  • Fix broken NPM release

v0.1.0

03 Sep 00:48
Compare
Choose a tag to compare
  • Initial release