Same with ISimpleType (if I add a property like x: types.number) and ISnapshottable (if I add a property that is based in another model such as obj: AreaProperties) actually

Hi, thanks for reporting! They are now exported as well on the main package and should be out with next release! :)
Can you please check if its ok by cloning the repository locally, building and npm install from local folder?
Thanks for your time! :)

seems to work :) the only annoying thing is WebStorm trying to optimize out the "unused" imports, but I guess that's a WebStorm problem (and using // noinspection ES6UnusedImports fixes it)

Ok actually another one when using types.map

import { IExtendedObservableMap } from 'mobx-state-tree/dist/types/complex-types/map'

PS: are maps required to have strings as keys or can they be numbers?

I updated the master branch, please check if its ok so I will cut a minor release :)

They only support strings as now due to a mobx limitation to support IE.
It will be supported on MobX 4, so keep tuned. :)
Most likely will be implemented in MST after as a separate type that will (most likely types.kvp = key value pair) that will be an observable map and serialized as an array of object with key and value properties.

Looking good! (though I didn't test all possible types so far)

Damned IE :) Am I right that the json serialization (snapshot) of a map then is a plain object?

@xaviergonz Yep, it is!

@xaviergonz Please note to always import from mobx-state-tree never from a specific file inside the dist build. That will mess up packaging etc. Sadly there is a popular VSCode plugin that does that by default :(

@mattiamanzati btw, we could more often use type instead of interface, which don't have the constraint they need to be exported :)

@mweststrate thanks, I wanted to, but I didn't have much of a choice :) I plan to fix the imports in my code as soon as the fix is out in npm