reactCompiler: true failing on next dev --turbopack and next build --turbopack #78163

followbl · 2025-04-14T20:29:55Z

Link to the code that reproduces this issue

https://github.com/followbl/react-compiler-bug

To Reproduce

ngl, the repo does not trigger the bug, it's happening in our monorepo and I was not able to reproduce via create-next-app

however in our monorepo simply turning reactCompiler on and off is causing this to be triggered with --turbopack build and dev server enabled

@app/www:build: The export usePathname was not found in module [project]/node_modules/next/navigation.js [app-client] (ecmascript).
@app/www:build: The module has no exports at all.
@app/www:build: All exports of the module are statically known (It doesn't have dynamic exports). So it's known statically that the requested export doesn't exist.
@app/www:build:
@app/www:build:
@app/www:build: ./node_modules/@vercel/speed-insights/dist/next/index.mjs:7:1
@app/www:build: Export useRef doesn't exist in target module
@app/www:build:    5 |
@app/www:build:    6 | // src/react/index.tsx
@app/www:build: >  7 | import { useEffect, useRef } from "react";
@app/www:build:      | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@app/www:build:    8 |
@app/www:build:    9 | // package.json
@app/www:build:   10 | var name = "@vercel/speed-insights";
@app/www:build:
@app/www:build: The export useRef was not found in module [project]/node_modules/next/dist/compiled/react-experimental/index.js [app-client] (ecmascript).
@app/www:build: The module has no exports at all.
@app/www:build: All exports of the module are statically known (It doesn't have dynamic exports). So it's known statically that the requested export doesn't exist.
@app/www:build:
@app/www:build:
@app/www:build: ./node_modules/@vercel/speed-insights/dist/next/index.mjs:168:1
@app/www:build: Export useSearchParams doesn't exist in target module
@app/www:build:   166 |
@app/www:build:   167 | // src/nextjs/utils.ts
@app/www:build: > 168 | import { useParams, usePathname, useSearchParams } from "next/navigation.js";
@app/www:build:       | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@app/www:build:   169 | var useRoute = () => {
@app/www:build:   170 |   const params = useParams();
@app/www:build:   171 |   const searchParams = useSearchParams() || new URLSearchParams();
@app/www:build:
@app/www:build: The export useSearchParams was not found in module [project]/node_modules/next/navigation.js [app-client] (ecmascript).
@app/www:build: The module has no exports at all.
@app/www:build: All exports of the module are statically known (It doesn't have dynamic exports). So it's known statically that the requested export doesn't exist

the reason I'm logging this is if I remove the --turbopack option, the build and dev server will run fine...

so it's either reactCompiler or --turbopack

yes, I have cleared and cleaned the cache on everything multiple times to confirm this is the issue.

Current vs. Expected behavior

current: build and dev server are failing
expected: build and dev server to run and complete

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.3.0: Thu Jan  2 20:24:16 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 22.13.1
  npm: 10.9.2
  Yarn: 1.22.21
  pnpm: 10.8.0
Relevant Packages:
  next: 15.3.1-canary.7
  eslint-config-next: N/A
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A

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

Turbopack, React

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

next dev (local)

Additional context

No response

The text was updated successfully, but these errors were encountered:

timneutkens · 2025-04-30T08:00:10Z

Ran the reproduction but there is no error, here's the codesandbox: https://codesandbox.io/p/github/followbl/react-compiler-bug/main. Can you provide a full reproduction?

github-actions · 2025-04-30T08:00:40Z

We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate.

Why was this issue marked with the `please add a complete reproduction` label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Next.js (next@canary) to make sure your issue has not already been fixed.

If you cannot create a clean reproduction, another way you can help the maintainers' job is to pinpoint the canary version of next that introduced the issue. Check out our releases, and try to find the first canary release that introduced the issue. This will help us narrow down the scope of the issue, and possibly point to the PR/code change that introduced it. You can install a specific version of next by running npm install next@<version>.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the please add a complete reproduction label that receives no meaningful activity (e.g. new comments with a reproduction link) are automatically closed and locked after 2 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without reproduction steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

nextjs-bot · 2025-05-04T23:42:37Z

This issue has been automatically closed due to 2 days of inactivity and the absence of a complete reproduction. If you believe this was done in error, please leave a comment. If you are experiencing a similar issue, consider opening a new issue with a complete reproduction. Thank you.

github-actions bot added React Related to React. Turbopack Related to Turbopack with Next.js. labels Apr 14, 2025

timneutkens added the please add a complete reproduction Please add a complete reproduction. label Apr 30, 2025

nextjs-bot added the stale The issue has not seen recent activity. label May 1, 2025

nextjs-bot closed this as not planned Won't fix, can't repro, duplicate, stale May 4, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

reactCompiler: true failing on next dev --turbopack and next build --turbopack #78163

reactCompiler: true failing on next dev --turbopack and next build --turbopack #78163

followbl commented Apr 14, 2025

timneutkens commented Apr 30, 2025

github-actions bot commented Apr 30, 2025

nextjs-bot commented May 4, 2025

reactCompiler: true failing on next dev --turbopack and next build --turbopack #78163

reactCompiler: true failing on next dev --turbopack and next build --turbopack #78163

Comments

followbl commented Apr 14, 2025

Link to the code that reproduces this issue

To Reproduce

Current vs. Expected behavior

Provide environment information

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

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

Additional context

timneutkens commented Apr 30, 2025

github-actions bot commented Apr 30, 2025

Why was this issue marked with the please add a complete reproduction label?

I added a link, why was it still marked?

What happens if I don't provide a sufficient minimal reproduction?

I did not open this issue, but it is relevant to me, what can I do to help?

I think my reproduction is good enough, why aren't you looking into it quicker?

Useful Resources

nextjs-bot commented May 4, 2025

Why was this issue marked with the `please add a complete reproduction` label?