Next.js 15 + React 19 breaks with “Cannot get 'react/jsx-dev-runtime'” and Invalid Hook Call errors

[tastypurgen]

Describe the bug

After upgrading a working project (and the official nextjs-ssr example) from Next.js 14 ↠ 15 and React 18 ↠ 19, the app fails to boot:

⨯ Error: Cannot get 'react/jsx-dev-runtime'
^in terminal

^in console

Reproduction:
The issue can be reproduced in the app from the examples repo:
https://github.com/module-federation/module-federation-examples/tree/master/nextjs-ssr
With the latest dependencies:

  "dependencies": {
    "@module-federation/nextjs-mf": "8.8.31",
    "lodash": "4.17.21",
    "next": "^15.3.3",
    "react": "^19.1.0",
    "react-dom": "^19.1.0",
    "webpack": "5.96.1"
  }

Reproduction

https://github.com/module-federation/module-federation-examples/tree/master/nextjs-ssr

Used Package Manager

pnpm

System Info

System:
    OS: Windows 11 10.0.26100
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 5.12 GB / 31.69 GB
  Binaries:
    Node: 20.19.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 11.4.1 - ~\AppData\Roaming\npm\npm.CMD
    pnpm: 10.12.1 - ~\AppData\Roaming\npm\pnpm.CMD
  Browsers:
    Edge: Chromium (131.0.2903.146)
    Internet Explorer: 11.0.26100.1882

Validations

• Read the docs.
• Read the common issues list.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Module federation issue and not a framework-specific issue.
• The provided reproduction is a minimal reproducible example of the bug.

[Anisha12311]

I have the same problem; is there a solution?

[tastypurgen]

@Anisha12311, only downgrade worked for me.
But in my case, it is not possible as my microFE has React 19, so I'm wait for a working solution with Next 15

[Anisha12311]

Here are my current dependencies:

  "dependencies": {
    "@module-federation/nextjs-mf": "^8.8.31",
    "next": "^15.3.3",
    "react": "^18.3.1",
    "react-dom": "^18.3.1"
  }

I am using the next js page router.
I encountered Trivy security vulnerabilities in Next.js 14, that's why I upgrade next js version from next js 14 to next js 15 version.
After upgrading from Next.js 14 to 15, I'm encountering same issues.

[tastypurgen]

@Anisha12311, in the next migration guide there is a mention that react 19 is required now, so it is the first thing I would do.
Additionally, regarding the microFE issue, I decided to switch to @module-federation/enhanced. This package worked for my setup

[ScriptedAlchemy]

v15 doesnt really work currently.

0.0.0-next-20250616235047 may do the job - its a early version of v9.

[tastypurgen]

Thanks @ScriptedAlchemy for the update.
Well, installing 0.0.0-next-20250616235047 at least allowed me to run the application, but I got errors related to react19.2-canary while I was using 19.1 on both sides. Other than that, I hadn't had a chance to dive deeper into this

[ScriptedAlchemy]

Is it pulling down more react chunks? Do you have repo or can we zoom call?
Next doesn't ever use whatever react you install. Its using next/dist/compiled/react etc.

[ScriptedAlchemy]

try this. https://github.com/ScriptedAlchemy/next-apps-ejected

It seems to work, note not all of nexts internals are shared in that version installed. so maybe like next/head or something brings in another copy of react or some other singleton that breaks it?

If you can reporoduce it there i can take a look.

[Anisha12311]

This worked for me.
useRouter should be imported from next/navigation.

"dependencies": {
  "@module-federation/nextjs-mf": "^8.8.23",
  "next": "^15.3.3",
  "react": "^19.1.0",
  "react-dom": "^19.1.0"
}

[ScriptedAlchemy]

That doesn't work tho. Next navigation just isn't shared.

[github-actions]

Stale issue message