Turbopack: more module ident collisions (#78207)
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.
Showing
Please
register
or
sign in
to comment