You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes two more module ident collisions
1. `ContextTransition` is a massive footgun, because it reuses the transitions from the parent context. So it essentially always creates a new context (which is not actually what we want), e.g. here this created two different `app-edge-shared` contexts because `app-edge-rsc` and `app-edge-ssr` have different transitions.
I hope this wasn't by design?
```
next/dist/esm/server/app-render/after-task-async-storage.external.js [app-edge-rsc]
->
next/dist/esm/server/app-render/after-task-async-storage-instance.js [app-edge-shared]
next/dist/esm/server/app-render/after-task-async-storage.external.js [app-edge-ssr]
->
next/dist/esm/server/app-render/after-task-async-storage-instance.js [app-edge-shared]
```
2. The client module proxy module was missing its layer in the identifier (the layer of the proxy module, i.e. `app-edge-rsc` or `app-rsc`). It's correct that there are two different modules.
Copy file name to clipboardExpand all lines: crates/next-core/src/next_client_reference/ecmascript_client_reference/ecmascript_client_reference_module.rs
0 commit comments