mobx-safe
Drop-in action
replacement for MobX that can handle errors before throwing.
; setTimeoutnew DangerZone.enter, 100;setTimeoutconsole.logcaughtErrors, 200; // [Error: Lana!]
Why
Generally, MobX recommends using native browser/Node error handling for uncaught errors. IE and older versions of Edge don't provide stack traces in certain cross-domain situations (link/link). In order to react to errors and guarantee call stacks you'll need to handle the errors yourself in the original execution stack. Knarly!
See this MobX issue.
Usage
action
Import action
from mobx-safe
and use as you would mobx
's action
.
That's it!
; ; // Error: What!?wrapped;
Basic method wrapping and TypeScript decorators are supported. Babel decorators are not supported.
caughtErrors
Type: IObservableArray<Error>
Synchronously pushed to whenever an action
error throws, before it's rethrown or handled.
Observe this to react to errors having been thrown.
;; autorun;
configure.clearOnCaughtErrorHandlers
Type: boolean
If given as true
, clears any handlers added for caught errors.
; configureMobXSafe;
configure.onCaughtError
Type: (handler: (error: Error) => void) => void
Adds a method to be called whenever an error is pushed to caughtErrors
.
These methods are called synchronously before caught errors are rethrown.
; configureMobXSafe;
If passed with clearOnCaughtErrorHandlers
, only the added onCaughtError
will be registered after configure
finishes.
Best Practices
Clear Between Tests
Multiple tests that interact with mobx-safe
can leave with multiple onCaughtError
handlers active.
Clear state after each test with configure.clearOnCaughtErrorHandlers
.
For example, in Jest and other test frameworks with afterEach
:
afterEach;