Paulus Schoutsen
Paulus Schoutsen
Starting with npm3 this has actually become a breaking change: > With the introduction of NPM3, peerDependencies behaves differently. It no longer actually installs the peerDependency packages. Instead, it just...
The reason the flag is there is because otherwise it will start dispatching an updated state to observers before all observers have been notified of the previous state. On Tue,...
The code has been updated since that commit and the master branch has it correct: https://github.com/optimizely/nuclear-js/blob/master/src/reactor.js#L140
No, the fix was included as part of v1.1 which was the first version to throw this exception.
I have [updated your fiddle](https://jsfiddle.net/acj30a5u/3/) with some log statements to give a better insight in what is going on. So it looks like when `app.setState` is called, it will directly...
Looked at a few other Flux implementations, they all raise errors too: - [Flux (Facebook)](https://github.com/facebook/flux/blob/master/src/Dispatcher.js#L181-L184) - [Fluxible (Yahoo)](https://github.com/yahoo/dispatchr/blob/master/lib/DispatcherContext.js#L57-L59) - [Fluxxor](https://github.com/BinaryMuse/fluxxor/blob/master/lib/dispatcher.js#L45-L49)
Another solution could be to queue the actions and process them once all observers have been called.
Observers can be called if you do this, see #130
That makes a lot more sense :)
This integration is for IronOS and not specific Pinecil 2. The integration should be called `ironos`