MobX Developer Tools
Dev-tools for MobX and React
Total ratings for MobX Developer Tools
3.37
(Rating count:
49)
User reviews summary
Pros
- Easy to initialize the dev tools without including the code
- Easier than installing the npm package mobx-react-devtools manually
- Good for react mobx development
Cons
- Freezes and generally doesn't work correctly
- Issues with connectivity - gets stuck on 'connecting'
- Poor compared to redux-devtools
- Has not been updated in a long time
- Lacks a scrollbar for large data sets
- Not useful for detecting error sources in Mobx
- Doesn't run on Microsoft Edge(webkit)
- Bug in the latest version
Most mentioned
- Scrollbar issue
- Freezing
- Poor compared to redux-devtools
- Connectivity issue
Upgrade to see all 30 reviews
Recent reviews for MobX Developer Tools
Recent rating average:
1.70
All time rating average:
3.37
Upgrade to see all 30 reviews
Rating filters
5 star
4 star
3 star
2 star
1 star
Date | Author | Rating | Lang | Comment |
---|---|---|---|---|
2022-09-13 | Artur Finger | Missing components and Performance tabs (in a React app). The only things I can inspect are changes (i.e. mobx actions). | ||
2022-08-09 | Akseli Nurmio | Freezes and just doesn't work. | ||
2022-01-03 | Daniel | It says "connecting..." forever and nothing happens. | ||
2021-12-26 | Temp | Almost useless, redux devtools a cut above | ||
2021-12-02 | Ahmed Kaja | Sadly, not updated for the last 2 years! | ||
2021-10-11 | David Munger | 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. | ||
2021-03-11 | 管融嘉 | can we have state tree? | ||
2020-10-15 | Konrad Broda | Missing scrollbar issue hasn't been fixed for a year now.. As someone said; poor compared to redux-devtools. | ||
2020-09-25 | 高科 | can not run on microsoft edge(webkit) | ||
2020-07-30 | 中国加油 | 不是很好用 |
Upgrade to see all 30 reviews