Avoid facade splits solely for export mangling (#99285)
## Summary A dynamically imported local-only ESM module could load through a facade while static named imports resolved to its locals module. For shared singletons, that meant two runtime identities. This backs off the facade split introduced for export mangling in #97770, addressing the remote-components regression reproduced in #99279. Modules with actual re-exports still split as before, and unsplit modules remain eligible for export-name mangling when their names can be changed safely. Escaping namespaces keep their original export names. Focused execution coverage checks that mixed dynamic/static imports register a single module identity; the affected namespace and snapshot expectations are updated. ## Verification - `cargo test -p turbopack-tests --test execution` — 311 passed. - `cargo test -p turbopack-tests --test snapshot` — 132 passed. - Turbopack ECMAScript unit suite — 590 passed. - `pnpm build-all`, `cargo fmt --all -- --check`, Prettier and lint-staged checks passed. - Both #99279 production Turbopack fixtures passed with shared-singleton assertions in a disposable checkout; those unmerged fixtures are not included here. <!-- NEXT_JS_LLM --> <!-- fleet faf1202d-c919-4f7d-bb74-d3fe954bbc57 --> --------- Co-authored-by:vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by:
Luke Sandberg <210140+lukesandberg@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment