Dion Dirza

@ctrlplusb @birkir i have bad message for you guys, this error still happened in feature/mobx branch. Exactly after you refresh on Counter page then click increment/decrement button.

@ctrlplusb just found pulled `react-tree-walker` in `node_modules` still 2.1.0 sean, probably you use exact version on its dependency. --- Update: found this on `react-async-bootstrapper` package.json ``` "react-tree-walker": "^2.1.0" ```

The problem caused by `yarn.lock` file here. Now it works fine. gr8

Anyways, I make a little experiment here. Try to call `counter.inc` function in `componentWillMount`, the server rendered result different with client rendered result Executed 2 times in server and 2...

Actually my concern is not maintain modified state to have same value both client and server. Instead I usually set flag in my store on componentWillMount and that flag has...

Cool, just look at it's README, gonna continue to try it tomorrow. It's pretty late here. Anyway good job guys.

I think this library would be worth to be included as standard for this boilerplate: - [nps](https://github.com/kentcdodds/nps) - [commitizen](https://github.com/commitizen/cz-cli) - [validate-commit-msg](https://github.com/conventional-changelog/validate-commit-msg)

Would prefer to migrate our config to using this [node-config](https://github.com/lorenwest/node-config/)

never try it before, will it replace happy pack usage?

@bost-h you can append this query in your polyfill.io src `&flags=gated,always`, this will solve issue both in IE and Apple device. So it will be like this: `https://cdn.polyfill.io/v2/polyfill.min.js?features=default,es6&flags=gated,always`