Alternatives to spy() for production env?

[nick-delirium]

Hi. I'm a maintainer from openreplay, we are making tracking tools to debug web sessions, and, of course, we have a mobx plugin that should (in theory) observe and track state changes and mutations, year ago, during its creation, original creator of that plugin used spy simply because its easiest way to achieve global level tracking without much troubles. Source code here

Well of course, it does not really work in production env since spy function returns no-op error.

Is there any approach to achieve similar or as close as possible functionality where we can observe mutations? In theory, we can let users attach listeners to every store, but its not the best or desirable approach.

[nick-delirium]

ok I guess I'm on my own here 👍

[mweststrate]

Mobx-utils.deepObserve or shipping the dev build for mobx are the closets things

…

On Tue, 13 Jun 2023, 14:44 Delirium, ***@***.***> wrote: Closed #3695 <#3695> as resolved. — Reply to this email directly, view it on GitHub <#3695>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN4NBGAOQUCSJBC7YAGMQLXLBODJANCNFSM6AAAAAAYHSGQ2I> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>