v4.3.1

• Change peer dependencies to reflect compatibility with latest MobX versions (#172)

Add non-breaking ESM support

• Add non-breaking ESM support
• Update exports map to handle some folder indices

Use catch instead of finally for browser compatibility in mutator

I am seeing lots of errors in Firefox and IE like Mutator (MutatorName) may not dispatch action (ActionName). And the callstack does not have a mutator in any of its stacks. When I look closer at the error, I see that these errors only happen in Firefox and IE so I think there is a browser compatibility issue where the finally is not getting recognized. I am going to switch over to a try catch instead to see if this fixes the issue

v4.2.4

• Fix global reference (#151)

v4.2.3

• Improve mutatorAction typings (#143)

Setting the name of the mutator instead of the name of the creating function

U/jarmit/fix mutator name (#141)

* Setting the name of the mutator instead of the name of the creating function

* 4.2.2

* fix tests

* Actually fix tests

* rename

Ensure mutators don't return a type through a build time error instead of a run time error

Ensure mutators don't return a type through a build time error instea…

…d of a run time error (#140)

* Ensure mutators don't return a type through a build time error instead of a run time error

Improve the error message for an action getting thrown inside a mutator

Improve the error message for an action getting thrown inside a mutat…

…or (#139)

* The error thrown when an action called inside a mutator should give more information

v4.1.0

• Change mutator actions to disallow them from returning values or being async (#130)
• Change mutators to use named MobX actions for a better experience with MobX dev tools (#133)

v4.0.1

• Change internal implementation to avoid unnecessary anonymous functions and reduce callstack depth (#124, #125)