Unhandled Runtime Error in v8.1.0-canary.4 due to Eager Consumption of Shared Module about universe HOT 12 CLOSED

I was able to reproduce this issue without any remotes in this codesandbox: https://codesandbox.io/p/sandbox/cocky-haslett-tttr38

from universe.

@ScriptedAlchemy seems it wan't lib issues, as i'm getting Shared module is not available for eager consumption randomly
like react, react-dom, jsx-dev-runtime
soon when revert to canary-1 all work as expected
see also
#1602 (comment)

from universe.

Try latest canary. I've found the cause of the eager issues raising up.

from universe.

Try latest canary. I've found the cause of the eager issues raising up.

latest canary is working well for me. @ScriptedAlchemy

from universe.

Do you have a reproduceable example?

from universe.

Do you have a reproduceable repo?

from universe.

@ScriptedAlchemy hey man
sorry seems that issue came from lottie lib, soon when i did remove from import lottie issue disappear
But let me double test again

from universe.

Do you have a reproduceable repo?

It is very hard to reproduce as it does it randomly

from universe.

This branch may resolve it, ive been able to reproduce it.
#1625

Ill work on another canary once im sure theres not other implications

from universe.

The problem seems to be around dependOn for entrypoints which messed with callback ordering, and my async cointainer hoisting only handled that chunk itself, not also chunks its depends on that are entrypoints. Since adding that to AsyncBoundaryPlugin, it seems to work

from universe.

Thanks @ScriptedAlchemy
Sorry for off topic do u have any ETA for app routers

from universe.

Thanks @ScriptedAlchemy

Sorry for off topic do u have any ETA for app routers

No immediate plans. There is a how to help section. But rsc will go to modernjs and remix first.
Watch those frameworks for signals.

from universe.