rsnext/test/e2e/app-dir/app-external
Jiachi Liu cd821c8e03
Fix nested esm package default import resolving mismatch (#57784)
For app router bundling layers "SSR rendering" and "browser" layer, which are used for server side rendering and client, we should still apply the module resolving rules to all assets since we bundled everything, removed the default exclude conditions as they'll not apply the rules to node_modules. That could cause the mismatch resolving for package.

E.g. You have two dual packages A and B are both compatible for ESM and CJS, and both have default export. B is depent on A, but when you import B in a client component that will be SSR'd, it's picking up the CJS asset like the case described in #57584 .

Fixes #57584 
Closes NEXT-1702
2023-10-31 00:31:23 +00:00
..
app Fix nested esm package default import resolving mismatch (#57784) 2023-10-31 00:31:23 +00:00
components Fix resolving for esm package with only exports.import condition (#42767) 2022-11-11 00:50:46 +00:00
node_modules_bak Fix nested esm package default import resolving mismatch (#57784) 2023-10-31 00:31:23 +00:00
pages Eagerly bundle external ESM dependencies for pages (#42741) 2022-11-10 18:11:38 +01:00
app-external.test.ts Fix nested esm package default import resolving mismatch (#57784) 2023-10-31 00:31:23 +00:00
middleware.js Pick esm main fields and condition names first for RSC server layer (#50548) 2023-06-08 16:24:03 +00:00
next.config.js Remove experimental config from create-next-app (#49241) 2023-05-05 00:22:28 -07:00