vercel__next.js/test/e2e/app-dir/app-external/next.config.js at codex/fallback-root-cache - vercel__next.js - GetSkill.work

skills/vercel__next.js

mirror of https://github.com/vercel/next.js.git synced 2026-09-20 02:25:18 +08:00

Files

T

Niklas Mischkulnig 47b9fc6128 Turbopack: Allow ESM externals in SSR (#70258 )

Closes PACK-3244
Closes https://github.com/vercel/next.js/issues/69562

Await the module in both environments (SSR/browser), if it's async in at
least one of them.

We can't and don't want to make the browser module async (artifically)
if the SSR module is async (due to ESM externals).

The only concern regarding `async` not always being true in the manifest
was that we don't want to await in non TLA cases (e.g. CJS exporting a
promise, etc...).
But the SSR module being ESM with TLA and the browser module being CJS
with a Promise export is exceedingly unlikely.

2024-10-01 14:41:21 +02:00

11 lines

253 B

JavaScript

Raw Permalink Blame History

 module.exports = {
   reactStrictMode: true,
   transpilePackages: ['css', 'font', 'transpile-ts-lib', 'transpile-cjs-lib'],
   serverExternalPackages: [
     'conditional-exports-optout',
     'dual-pkg-optout',
     'transitive-external',
     'esm',
   ],
 }