MobX Developer Tools MobX Developer Tools

Developer Tools
Version: 0.9.26
Last Update: 2020-10-30

Overview

MobX Developer Tools is a Chrome extension developed by Andy Kogut. According to the data from Chrome web store, current version of MobX Developer Tools is 0.9.26, updated on 2020-10-30.
30,000+ users have installed this extension. 49 users have rated this extension with an average rating of .

Dev-tools for MobX and React

Inspect mobx-react observers. Edit values in observable objects (Doesn't support editing react props/state, use react-devtools for that)
Track changes in MobX observables
MST support

Rating

49 ratings

Total Installs

30,000+

Information

Last Update

2020-10-30

Current Version

0.9.26

Size

875KiB

Author

Andy Kogut

Website

None

Category

Developer Tools

Latest Reviews

See More

avatar Daniel
2022-01-03

It says "connecting..." forever and nothing happens.

avatar Temp
2021-12-26

Almost useless, redux devtools a cut above

avatar Ahmed Kaja
2021-12-02

Sadly, not updated for the last 2 years!

avatar David Munger
2021-10-11

It's a bare minimum of useful, although it defaults to doing nothing unless you click a button called 'record', which is not what you would expect. Turns out 'record' actually means it turns logging on, just like logging in the network tab. To make matters worse, 'record' (i.e., log changes), is off by default.

Another strange thing is that if you click 'Open Mobx Dev Tools' from the context menu, it opens an empty browser window, which remains empty (just blank white page) no matter what you do. I could only see anything by using the Mobx tab in the standard dev tools pane.

Finally, it did nothing to help with my #1 frustration with Mobx, which is that sometimes I get errors about 'wrappedComponent' coming from an observer, and it's impossible to tell which of my components is causing the error, much less why, since it points to the mobx library code. It is simply not possible to find what line of my own code actually caused the error. I was hoping these dev tools would help by enhancing these error messages, or at a bare minimum, at LEAST showing which 'wrappedComponent' triggered the error. Unfortunately, it does none of this.

avatar 管融嘉
2021-03-11

can we have state tree?