by timarney

Capture errors in production and replay them locally with Redux Dev Tools

124 Stars 3 Forks Last release: Not found MIT License 36 Commits 0 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:


Direct Integration with Dev Tools IMAGE ALT TEXT

See this branch .

Futher info here

The Goal

This project aims to combine Error tracking with Redux Dev Tools to capture errors and user actions from a production setting.

Use Case

  1. Redux Middleware is setup to capture an array of actions when an error is thrown on (live version)
  2. Aug 15th 8pm -> User visits error is thrown (log of actions is captured)
  3. Aug 16th 10am -> Developer loads the logged actions into local version of (dev version)
  4. Redux Dev Tools replay the actions recreate the state to the point where the error happened for debugging


When an error is thrown it is captured by TrackJS. The users actions up to the error point get logged for later retrieval. The error in TrackJS references the log which can imported into a local environment via Redux Dev Tools

  1. Dowload the reported file
  2. Import via the Redux Dev Tools
  3. The actions are automatically replayed to get back to the error state
  4. Debug

Note: The master branch of this repo saves to a JSON file for import back to Dev Tools.
The remote-dev-tools branch integrates directly with Dev Tools and uses remotedev-server for saving the actions.


  1. Update index.html enter your TrackJS token
  2. npm install
  3. npm start


Error tracking services such as TrackJS offer great insights into where errors happen. They give us stack traces, network information, grouped error reports and much more.

Redux + Redux Dev Tools give us the ability to step-through state and toggle actions. We can replay and even export / import state when developing locally.

If an error is thrown in production it would be amazing to get the

Error Report
and also be able to see what actions happened leading up to that error. Essentially getting your local development enviroment / app back to the state where the error occured so you can debug locally.

The Inspiration

I was listening to @react30 ... at about this point :bulb: :bulb: :bulb:

So I tried something and tweeted about it and here we are (check the note about the future below).

For more inspiration

Check out @jrullmann

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.