Sven Sauleau

I believe this transformation is simpler: ### Input ```js const Counter = ({ text }, { val } = { val: 0 }, setState) => ( {text} setState({ val: val...

Yes, that's correct. Your first solution is good. You could also pass `this` as argument (and rename it) instead of binding it to the instance. It will maybe help for...

```js function _temp(self) { self.setState({ val: self.state.val - 1 }); } function _temp2(self) { self.setState({ val: self.state.val + 1 }); } class Counter extends React.Component { constructor() { super(); this.state...

You load them from [bundle.run](https://bundle.run/) which is a Rollup/Browserify as a service with a CDN.

Are you seeing an error? `async-reactor` is taking advantage of the `import` function but it has no control on it, it's likely your bundler that fails.

have you tried to remove node_modules and reinstall it?

What bundler are you using? I can't really tell what's the issue, but it seems to me that the bundler isn't resolving the asset. If the import() returns a promise,...

Interesting issue, thanks for your report. How do you unmount Screen 1 and mount screen 2? It should probably be only one rendering tick. Could you please share an example...

Yes, I can see it blinking. I have a similar example [here](https://github.com/xtuc/async-reactor/tree/master/examples/React-router). It doesn't seem to be blinking to me, could you please try?

Sorry I may have misunderstood you then. You're saying that the loader shouldn't show up because it cause a blinking, is that correct?