Barrel optimizer (optimizeImports) breaks RSC Components bundler: Could not find the module in the React Client Manifest

[florianliebig]

Link to the code that reproduces this issue or a replay of the bug

https://github.com/florianliebig/next-error-optimize-package-imports

To Reproduce

Checkout example repo

pnpm i && pnpm build

Steps to create error:

1. Use pnpm or import any external dep with server & client components in same wildcard export (in this case index.tsx exporting simple ClientComponent & ServerComponent
2. Adjust next.config.json to use experimental optimizePackageImports from Improve barrel optimizer with loader caching and wilcard exports #54695
3. Import both server & client component in one page from barrel file
4. Build and / or start and see the error "Could not find the module ... in the React Client Manifest"

Current vs. Expected behavior

Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Could not find the module "/Users/florianliebig/code/next-error-optimize-package-imports/packages/components/src/client/client-component.tsx#ClientComponent" in the React Client Manifest. This is probably a bug in the React Server Components bundler.

I would expect both Server & client components to be optimized properly from #54695

import { ClientComponent, ServerComponent } from '@shared/components';

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:17:35 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T8112
    Binaries:
      Node: 18.16.0
      npm: 9.6.7
      Yarn: 1.22.19
      pnpm: 8.6.2
    Relevant Packages:
      next: 13.5.3-canary.0
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: N/A

Which area(s) are affected? (Select all that apply)

App Router, SWC transpilation

Additional context

No response

[florianliebig]

Possibily similar issue as in #55029

[florianliebig]

@shuding is this something you already ran into when building the "optimizePackageImports" process? Or are mixed client- & server components not a usecase here?

I was also not able to workaround this by splitting the imports in a file by server- & client components unfortunately.

[florianliebig]

I was able to narrow the issue down to

"mod.buildInfo.rsc" being undefined

Called from

next.js/packages/next/src/build/webpack/plugins/flight-client-entry-plugin.ts

Line 624 in 0bfd480

if (isClientComponentEntryModule(mod)) {

[shuding]

I'll take a look at this today 🙏

[songhobby]

I'll take a look at this today 🙏

Hi @shuding are there any updates or temporary fixes for this issue?

[osehmathias]

👀

[bartlangelaan]

Dirty workaround is to hack Next.js so the optimizePackageImports option is fully disabled (if you are encountering this with an automatically-enabled module).

You can do this with the patch-package module. Patch:

patches/next+13.5.2.patch

diff --git a/node_modules/next/dist/server/config.js b/node_modules/next/dist/server/config.js
index efd81cf..10b1d4a 100644
--- a/node_modules/next/dist/server/config.js
+++ b/node_modules/next/dist/server/config.js
@@ -507,7 +507,7 @@ function assignDefaults(dir, userConfig, silent) {
     if (!result.experimental) {
         result.experimental = {};
     }
-    result.experimental.optimizePackageImports = [
+    result.experimental.optimizePackageImports = [] || [
         ...new Set([
             ...userProvidedOptimizePackageImports,
             "lucide-react",

After this, everything started working again. Related: #55566, #55609.

Note: of course this is an unsupported workaround that may also break at any time.

[shuding]

Apologize for the delay! I just found the root cause to this and will open a PR to fix it today. Meanwhile what @bartlangelaan mentioned can be a temporary workaround.

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.