Nested AsyncComponents not resolved server-side about react-async-component HOT 6 CLOSED

Fixed in the alpha release. 😊

from react-async-component.

Hey @cpeddecord

Sorry just a quick one from me, but hopefully this helps.

I think this may be a side effect of you dynamically creating async component instances. Try lifting your createAsyncComponent(... calls to a place where they are statically bound, i.e. outside of the body of a function.

Internally I have to try and keep some sort of identifier going so that I can know which async component instances get rendered. With dynamic creation this number will keep ticking and I won't be able to marry up the instances for the resulting render within the withAsyncComponents handler.

from react-async-component.

@ctrlplusb thanks for the note! I'll give it a try and see if I can't get it working :)

from react-async-component.

Hey @cpeddecord

I have been working on a new version of this lib and during the refactor I think I may have spotted a bug that could lead to the behaviour you described. I think I have it fixed in the next branch. Don't use this branch yet though as it is in active development. But I thought I would let you know in the interim.

from react-async-component.

@ctrlplusb yaay

from react-async-component.

A word of warning though, don't use as of yet. I am still doing the rounds on it. :)

from react-async-component.