rsnext/test/e2e/app-dir/app-external/app
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
..
async-storage build: fix externals resolution when importing from next/dist (#55269) 2023-09-12 10:26:34 +00:00
client-dep Fix package resolution issue in app dir (#43349) 2022-11-25 01:19:21 +00:00
css Eagerly bundle external ESM dependencies for pages (#42741) 2022-11-10 18:11:38 +01:00
esm Fix nested esm package default import resolving mismatch (#57784) 2023-10-31 00:31:23 +00:00
esm-client-ref Fix client boundary defined in a module (#46171) 2023-02-21 15:20:45 +00:00
external-imports Fix resolving for esm package with only exports.import condition (#42767) 2022-11-11 00:50:46 +00:00
font Eagerly bundle external ESM dependencies for pages (#42741) 2022-11-10 18:11:38 +01:00
react-server Prefer module over main on main fields for app router server compiler (#56960) 2023-10-19 16:06:47 +00:00
shared-esm-dep Eagerly bundle external ESM dependencies for pages (#42741) 2022-11-10 18:11:38 +01:00
wildcard Fix conflict when re-exporting multiple Client References (#49468) 2023-05-16 12:35:12 +02:00
layout.js Eagerly bundle external ESM dependencies for pages (#42741) 2022-11-10 18:11:38 +01:00