Skip to main content
GoodFirstPicks
DashboardIssuesReposLeaderboard

GoodFirstPicks by Leaveitblank © 2026

CreatorRequest a RepoPrivacy PolicyTerms of Service
Bug: React 19 cannot run apps in both dev & production mode simultaneously | GoodFirstPicks

Bug: React 19 cannot run apps in both dev & production mode simultaneously

facebook/react 31 comments 1mo ago
View on GitHub
highopenScope: somewhat clearSkill match: noReactJavaScriptTypeScript

Why this is a good first issue

This involves deep React runtime compatibility issues between dev and prod modes.

AI Summary

The issue reports incompatibility between React 19 dev and prod builds when used together in micro frontend architectures, which worked in React 18. This appears to be a core runtime behavior change that would require React team investigation, as evidenced by multiple complex workarounds from the community.

Issue Description

Unable to run multiple React micro frontends (MFEs) when they don't all use the same NODE_ENV. When developing large systems using micro frontends (e.g. via module federation), it is not feasible for developers to have every MFE running locally. Instead, a proxy config can be used to pull built artifacts of existing MFEs and only run relevant apps locally. This worked well in React 18, but does not in React 19.

React version: 19

Steps To Reproduce

  1. Using some MFE solution (in my example, module federation), run a host app in dev mode (NODE_ENV === 'development') and a remote app in prod mode (NODE_ENV === 'production')
  2. Note that the runtimes are not compatible.

Link to code example: https://github.com/rdenman/react-19-mixed-env-mf

The current behavior

Unable to run mixed builds (dev + prod)

The expected behavior

Both dev and prod builds should be compatible.

This is the error I see when running the attached example. Note that downgrading the example to React 18 fixes this issue, and running both apps in either dev or prod mode also resolves the issue. <img width="705" alt="Screenshot 2025-01-08 at 7 59

GitHub Labels

Status: Unconfirmed

Want to work on this?

Claim this issue to let others know you're working on it. You'll earn 10 points when you complete it!

Risk Flags

  • core runtime behavior
  • potential architectural changes
  • multiple workarounds exist
Loading labels...

Details

Points10 pts
Difficultyhigh
Scopesomewhat clear
Skill Matchno
Test Focusedno