Effector-inspector has memory management problem, lacks live updates. #40
Description
Hi!
I noticed that the inspector creates a lot of DOM nodes and objects in memory to display everything (store, event, effect, etc...) without any constraints on size. Maybe it's not noticeable on small projects, but it quickly adds up and at some point, it becomes a problem because a page with a running dev environment can consume 3-4 GB of memory and more just because of the inspector itself.
Also, there is no way to see real-time updates in any inspector tab.