Chris Feijoo

I will check that after work. Some work needs to be done on Monolite to be adapted to last TypeScript features.

## Proxy The problem comes from the fact that the accessor function takes as argument a Proxy created by Monolite, which is returned recursively to take all accessors from root....

I see that you also did like the last comment in https://github.com/Microsoft/TypeScript/issues/16#issuecomment-330305477. ;) This Optional Chaining Operator is something I'm waiting for too. Monolite maybe needs to be reworked to...

I just saw this new library https://github.com/facebookincubator/idx. It uses the same trick of accessor function, though they don't seem to use the same runtime Proxy-based resolution. It makes me think...

@spacejack This is something that I'm already aware, but did not take time to fix: You can check https://github.com/kube/monolite/issues/2 for more information. I'm currently working on Electron applications, so I...

Just a little question about what your target is: If you target browsers in general, and performance in old browsers (those that do not support ES2015) is not a real...

I will add support for ES5 this week-end.

Just for info, I started the Babel plugin: https://github.com/kube/babel-plugin-monolite You can already install it using [NPM](https://www.npmjs.com/package/babel-plugin-monolite) ``` npm install --save-dev babel-plugin-monolite ``` It's still in really early stage, but I...

@bryanerayner Just did a little Google search, and the first article seems to say that performance is not heavily impacted by usage of Proxy: http://dealwithjs.io/es6-features-10-use-cases-for-proxy/#performance But one thing is that...

Yes I'm gonna try to do that when I have some time.