mirror of
https://github.com/reduxjs/redux-devtools.git
synced 2024-11-22 09:36:43 +03:00
59 lines
2.6 KiB
Markdown
59 lines
2.6 KiB
Markdown
Redux DevTools
|
|
=========================
|
|
|
|
A better README is coming. But if you insist...
|
|
|
|
<img src='http://i.imgur.com/HMW2pjP.png' width='700'>
|
|
|
|
### Installation
|
|
|
|
It's out on NPM as `redux-devtools@0.1.0`.
|
|
|
|
[This commit](https://github.com/gaearon/redux-devtools/commit/0a2a97556e252bfad822ca438923774bc8b932a4) should give you an idea about how to add Redux DevTools for your app **but make sure to only apply `devTools()` in development!** In production, this will be terribly slow because actions just accumulate forever. (We'll need to implement a rolling window for dev too.)
|
|
|
|
For example, in Webpack, you can use `ProvidePlugin` to turn magic constants like `__DEV__` into `true` or `false` depending on the environment, and import and render `redux-devtools` conditionally behind `if (__DEV__)`. Then, if you have an Uglify step before production, Uglify will eliminate dead `if (false)` branches with `redux-devtools` imports. Here is [an example](https://github.com/erikras/react-redux-universal-hot-example/compare/66bf63fb0f23a3c264a5d37c3acb4c047bf0c0c9...c6515236a1def8a3d2bfeb8f6cd6f0ccdb2f9e1b) of adding React DevTools to a project handling the production case correctly.
|
|
|
|
### Running Examples
|
|
|
|
You can do this:
|
|
|
|
```
|
|
git clone https://github.com/gaearon/redux-devtools.git
|
|
cd redux-devtools
|
|
npm install
|
|
|
|
cd examples/counter
|
|
npm install
|
|
npm start
|
|
open http://localhost:3000
|
|
```
|
|
|
|
Try clicking on actions in the log, or changing some code inside `examples/counter/reducers/counter`.
|
|
For fun, you can also open `http://localhost:3000/?debug_session=123`, click around, and then refresh.
|
|
|
|
Oh, and you can do the same with the TodoMVC example as well.
|
|
|
|
If you only would like to monitor a part of the state, you can set a select-prop on the DevTools component.
|
|
ex. `<DevTools select={state => state.todos} store={store} monitor={LogMonitor} />`
|
|
|
|
|
|
### It's Ugly!
|
|
|
|
The design or usability is not the point. (Although we'll have better design in the future :-)
|
|
|
|
**You can build a completely custom UI for it** because `<DevTools>` accepts a `monitor` React component prop. The included `LogMonitor` is just an example.
|
|
|
|
**[In fact I challenge you to build a custom monitor for Redux DevTools!](https://github.com/gaearon/redux-devtools/issues/3)**
|
|
|
|
Some crazy ideas for custom monitors:
|
|
|
|
* A slider that lets you jump between computed states just by dragging it
|
|
* An in-app layer that shows the last N states right in the app (e.g. for animation)
|
|
* A time machine like interface where the last N states of your app reside on different Z layers
|
|
* Feel free to come up with and implement your own! Check `LogMonitor` propTypes to see what you can do.
|
|
|
|
|
|
### License
|
|
|
|
MIT
|