Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix [Turbopack] next/root-params has no exports when rootParams: true is enabled [14 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#92744•Fetched 2026-04-15 06:18:33
View on GitHub
Comments
14
Participants
2
Timeline
21
Reactions
0
Author
pomathieupomathieu
Participants
icyJosephicyJosephpomathieupomathieu
Timeline (top)
commented ×14subscribed ×4mentioned ×2closed ×1

Code Example

Operating System: macOS Darwin 24.6.0
Next.js: 16.2.3
Node.js: v25.8.2
Turbopack: stable (default)

---

git clone https://github.com/pomathieu/nextjs-rootparams-turbopack-repro
cd nextjs-rootparams-turbopack-repro
npm install
npm run build

---

Export locale doesn't exist in target module
The module has no exports at all.

---

Operating System:
  Platform: darwin
  Arch: arm64
Next.js: 16.2.3
Node.js: 25.8.2
Package Manager: npm
RAW_BUFFERClick to expand / collapse

Verify canary release

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

Provide environment information

Operating System: macOS Darwin 24.6.0
Next.js: 16.2.3
Node.js: v25.8.2
Turbopack: stable (default)

Which area(s) are affected?

Turbopack

Link to the code that reproduces this issue

https://github.com/pomathieu/nextjs-rootparams-turbopack-repro

To Reproduce

git clone https://github.com/pomathieu/nextjs-rootparams-turbopack-repro
cd nextjs-rootparams-turbopack-repro
npm install
npm run build

Build fails with:

Export locale doesn't exist in target module
The module has no exports at all.

Current vs. Expected behavior

Current: Turbopack does not generate named exports from next/root-params. The module remains empty.

Expected: With rootParams: true, Turbopack should generate exports like locale() based on the [locale] dynamic segment, as described in the docs.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
Next.js: 16.2.3
Node.js: 25.8.2
Package Manager: npm

Which area(s) are affected?

Turbopack, App Router, PPR

Additional context

This blocks all i18n libraries (next-intl, lingui, intlayer) from working with cacheComponents: true:

Created from create-next-app@latest + next-intl + rootParams: true + cacheComponents: true.

extent analysis

TL;DR

The issue can likely be resolved by updating the configuration or waiting for a fix in a future version of Next.js or Turbopack, as the current setup with rootParams: true and cacheComponents: true is causing Turbopack to fail generating named exports from next/root-params.

Guidance

  • Verify that the issue persists with the latest versions of Next.js and Turbopack to ensure it's not already fixed in a newer release.
  • Check the documentation and issues for next-intl, lingui, and intlayer to see if there are any known workarounds or temporary fixes for the i18n libraries compatibility issue with cacheComponents: true.
  • Test disabling cacheComponents: true to see if it resolves the build issue, although this might not be a viable long-term solution.
  • Monitor the issues linked in the additional context (e.g., https://github.com/amannn/next-intl/issues/1493, https://github.com/vercel/next.js/issues/86870) for updates on when a fix might be available.

Example

No specific code snippet can be provided without more context on the exact configuration and code changes made to enable rootParams: true and cacheComponents: true, but reviewing the reproducible example provided (https://github.com/pomathieu/nextjs-rootparams-turbopack-repro) might offer insights.

Notes

The issue seems to be related to the interaction between Turbopack, Next.js, and the specific configuration options rootParams: true and cacheComponents: true. Without more information on future releases or patches, providing a definitive fix is challenging.

Recommendation

Apply workaround: Given the current information, the best course of action might be to disable cacheComponents: true until a fix is available in Next.js or Turbopack that properly supports this configuration with rootParams: true. This is because disabling cacheComponents: true might mitigate the build issue, even if it's not an ideal solution for performance reasons.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#search optimization#API routing#API middleware#SSR setup#ISR setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix [Turbopack] next/root-params has no exports when rootParams: true is enabled [14 comments, 2 participants]