nextjs - 💡(How to fix) Fix CPU doesn't support the bmi2 instructions [1 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#91671Fetched 2026-04-08 01:02:20
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×2closed ×1commented ×1issue_type_added ×1

Code Example

Node.js v24.14.0

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 7894
  Available CPU cores: 4
Binaries:
  Node: 24.14.0
  npm: 11.9.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.2.0
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

N/A

To Reproduce

  1. Install the latest version of next.js (pnpm create next-app@latest)
  2. Start the dev server (pnpm dev)

Current vs. Expected behavior

<img width="1222" height="598" alt="Image" src="https://github.com/user-attachments/assets/85212bf2-cebd-4ae6-b0ea-6837dc09bc1f" />

Provide environment information

Node.js v24.14.0

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 7894
  Available CPU cores: 4
Binaries:
  Node: 24.14.0
  npm: 11.9.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.2.0
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

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

Turbopack

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

next dev (local)

Additional context

The issue seems to go away when I use webpack instead of Turbopack. (pnpm dev --webpack)

extent analysis

Fix Plan

The fix involves disabling Turbopack and using Webpack instead for the development server.

Steps to Fix

  • Run the development server with the --webpack flag:

pnpm dev --webpack

* Alternatively, you can disable Turbopack in your `next.config.js` file by adding the following code:
  ```javascript
module.exports = {
  //... other configurations
  turbopack: false,
}

Then, run the development server as usual:

pnpm dev

Verification

Verify that the issue is resolved by checking the development server's behavior and the application's functionality.

Extra Tips

  • If you want to use Turbopack, you may need to update your next.config.js file to include Turbopack-specific configurations or wait for a fix in a future version of Next.js.
  • You can also try updating Next.js and its dependencies to the latest versions to see if the issue is resolved.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING