• Fixed #327: spy not working with runInAction

Introduced whyRun:

Usage:

• whyRun()
• whyRun(Reaction object / ComputedValue object / disposer function)
• whyRun(object, "computed property name")

whyRun is a small utility that can be used inside computed value or reaction (autorun, reaction or the render method of an observer React component) and prints why the derivation is currently running, and under which circumstances it will run again. This should help to get a deeper understanding when and why MobX runs stuff, and prevent some beginner mistakes.

This feature can probably be improved based on your feedback, so feel free to file issues with suggestions!

Semantic changes:

• @observable is now always defined on the class prototypes and not in the instances. This means that @observable properties are enumerable, but won't appear if Object.keys or hasOwnProperty is used on a class instance.
• Updated semantics of reaction as discussed in #278. The expression now needs to return a value and the side effect won't be triggered if the result didn't change. asStructure is supported in these cases. In contrast to MobX 2.2, effects will no longer be run if the output of the expression didn't change.

Enhancements

• Introduces isAction(fn) #290
• If an (argumentless) action is passed to observable / extendObservable, it will not be converted into a computed property.
• Fixed #285: class instances are now also supported by toJS. Also members defined on prototypes which are enumerable are converted.
• Map keys are now always coerced to strings. Fixes #308
• when, autorun and autorunAsync now accept custom debug names (see #293, by @jamiewinder)
• Fixed #286: autoruns no longer stop working if an action throws an exception
• Implemented runInAction, can be used to create on the fly actions (especially useful in combination with async/await, see #299
• Improved performance and reduced mem usage of decorators signficantly (by defining the properties on the prototype if possible), and removed subtle differences between the implementation and behavior in babel and typescript.
• Updated logo as per #244. Tnx @osenvosem!

2.2.2:

• Fixed issue #267: exception when useStrict(true) was invoked in combination with @observable attributes when using Babel
• Fixed issue #269: @action in combination with typescript targeting ES6 and reflect.ts
• Improved compatibility with JSON.stringify, removed incorrect deprecation message
• Improved some error messages

2.2.1

• Fixed issue where typescript threw a compile error when using @action without params on a field
• Fixed issue where context was accidentally shared between class instances when using @action on a field

2.2.0

See the release announcement for the full details of this release:

Introduced:

• action / @action
• intercept
• spy
• reaction
• useStrict
• improved debug names
• toJSON was renamed to toJS
• observable(asMap()) is the new idiomatic way to create maps
• the effect of when is now untracked, similar to `reaction.
• extras.trackTransations is deprecated, use spy instead
• untracked has been undeprecated
• introduced / documented: getAtom, getDebugName, isSpyEnabled, spyReport, spyReportStart, spyReportEnd
• deprecated extras.SimpleEventEmitter
• array splice events now also report the added collection and removedCount

2.1.7

• Fixed a false negative in cycle detection, as reported in #236

2.1.6

• Fixed #236, #237 call stack issues when working with large arrays

2.1.5

• Fix #222 (by @andykog) run observe callback of computed properties in untracked mode.

2.1.4

• Fixed #201 (see also #160), another iOS enumerability issue... By @luosong

2.1.3

• Fixed #191, when using babel, complex field initializers where shared. By @andykog
• Added lib/mobx.umd.min.js for minified cdn builds, see #85

2.1.2

• Improved debug names of objects created using a constructor
• Fixed(?) some issues with iOS7 as reported in #60 by @bstst

2.1.1

• Fixed issue where autoruns created inside autoruns were not always kicked off. (mobx-react's observer was not affected). Please upgrade if you often use autorun.
• Fixed typings of mobx.map, a list of entries is also acceptable.
• (Experimental) Improved error recovery a bit further

2.1.0

• MobX is now chatty again when an exception occurs inside a autorun / computed value / React.render. Previously this was considered to be the responsibility of the surrounding code. But if exceptions were eaten this would be really tricky to debug.
• (Experimental) MobX will now do a poor attempt to recover from exceptions that occured in autorun / computed value / React.render.

2.0.6

• resetGlobalState is now part of the mobx.extras namespace, as it is useful for test setup, to restore inconsistent state after test failures.
• resetGlobalState now also resets the caches of createTransformer, see #163.

2.0.5

• WIP on bower support

2.0.4

• $transformId property on transformed objects should be non-enumerable. Fixes #170.

2.0.3

• Always peek if inspecting a stale, computed value. Fixes #165.

2.0.2

• Fixed issue where changing an object property was tracked, which could lead to unending loops in autorunAsync.

2.0.1

• Undeprecated observable(scalar) (see 143)
• expr no longer prints incorrect deprecated messages (see 143)
• Requires mobx twice no longer fails.

2.0.0