How to fix Minified React error #123; visit https://react.dev/errors/123 for the full message in React

ReactINTERMEDIATECRITICALUpdated Dec 10, 2025· 106 views

React minified error #123 occurs when the internal reconciliation transaction class or batching strategy is not properly injected into React's update system, typically indicating a setup or initialization issue.

Quick fix

Fixes REACT_123

# If using Create React App
npm start  # Uses development build by default

# If using custom setup, ensure NODE_ENV is not set to production
NODE_ENV=development npm start
  1. Switch to the development build to see the full error
  2. Verify your React installation is complete
  3. Clean rebuild your production bundle
  4. Check your build configuration for React handling
react — error
# If using Create React App
npm start  # Uses development build by default
# If using custom setup, ensure NODE_ENV is not set to production
NODE_ENV=development npm start
Minified React error #123; visit https://react.dev/errors/123 for the full message

What this error means

This error occurs in React's minified production build when the internal reconciliation transaction class or batching strategy has not been properly configured. React uses an internal transaction system to batch updates and manage how the reconciler processes changes to the DOM. When error #123 appears, it means this core system is misconfigured or incompletely initialized, preventing React from properly handling state updates, prop changes, and DOM reconciliation. This is fundamentally a configuration problem rather than a logic error in your component code—it indicates that React itself hasn't been properly set up to run.

Typical symptoms

  • Entire application fails to render or becomes unresponsive
  • Updates to state or props are not processed correctly
  • Console shows the minified error #123 message in production
  • Application works fine in development but fails in production build
  • React throws an error immediately on application initialization

Common causes

  1. React library files are corrupted or incomplete in the production build
  2. Build process failed to properly bundle or minify React
  3. Using an outdated, incompatible, or partially installed version of React
  4. Custom build configuration interferes with React's internal initialization
  5. Webpack or bundler configuration strips or mangles React's internal setup code
  6. Node modules are not properly installed or dependencies are broken

How to fix "Minified React error #123; visit https://react.dev/errors/123 for the full message"

1Switch to the development build to see the full error

In development, React provides detailed error messages instead of minified codes. This will show you exactly what initialization step failed.

bash
# If using Create React App
npm start  # Uses development build by default

# If using custom setup, ensure NODE_ENV is not set to production
NODE_ENV=development npm start

The development build will reveal the actual problem causing error #123.

2Verify your React installation is complete

Check that React and ReactDOM are properly installed and match compatible versions.

bash
npm list react react-dom

# Should show something like:
# react@18.2.0
# react-dom@18.2.0

# If versions don't match or are missing, reinstall
rm package-lock.json node_modules
npm install

Ensure both react and react-dom are present in package.json dependencies.

3Clean rebuild your production bundle

Delete the build output directory and rebuild from scratch to ensure the production build is created correctly.

bash
# For Create React App
npm run build

# For custom setup (example)
rm -rf dist/
npm run build

# For Webpack
rm -rf dist/
webpack --mode production

A clean rebuild often resolves issues caused by incomplete or corrupted build artifacts.

4Check your build configuration for React handling

If using a custom webpack or build configuration, verify that React's initialization code is not being stripped or mangled.

javascript
// webpack.config.js - example
module.exports = {
  mode: 'production',
  entry: './src/index.js',
  output: {
    filename: 'bundle.js',
    path: __dirname + '/dist',
  },
  // Ensure no aggressive tree-shaking or mangling of React internals
  optimization: {
    usedExports: true,
    // Avoid over-aggressive minification
    minimize: true,
  },
};

Refer to your bundler's documentation for proper React handling.

5Update React to the latest stable version

Update to the latest stable version of React and ReactDOM to ensure all fixes and initialization code are included.

bash
npm update react react-dom

# Or specify a specific version
npm install react@latest react-dom@latest

If you're on an old version, update to a newer stable release. Check [React's release notes](https://react.dev) for any known initialization issues.

6Verify the entry point initializes React correctly

Ensure your application entry point (typically src/index.js or src/main.js) properly imports and initializes React and ReactDOM.

javascript
// src/index.js
import React from 'react';
import ReactDOM from 'react-dom/client';
import App from './App';

const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(
  <React.StrictMode>
    <App />
  </React.StrictMode>
);

Missing or incorrect initialization will prevent React's internal systems from setting up properly.

Advanced notes

Error #123 is a rare but serious sign of a broken React setup. It's not a bug in your component code—it's a configuration or build process issue. The minified production build intentionally strips full error messages to reduce bundle size, so switching to the development build is essential for debugging. In older versions of React (pre-16), this error could occur with certain custom setups or when using middleware that wasn't fully compatible. Modern React versions are more robust, so upgrading often resolves this issue. If you're building a custom JavaScript bundler or modifying React's core initialization, ensure you're not accidentally breaking the transaction/batching system that React depends on.

Frequently asked questions

What does "REACT_123" mean?
This error occurs in React's minified production build when the internal reconciliation transaction class or batching strategy has not been properly configured. React uses an internal transaction system to batch updates and manage how the reconciler processes changes to the DOM. When error #123 appears, it means this core system is misconfigured or incompletely initialized, preventing React from properly handling state updates, prop changes, and DOM reconciliation.
How do I fix "REACT_123"?
React minified error #123 occurs when the internal reconciliation transaction class or batching strategy is not properly injected into React's update system, typically indicating a setup or initialization issue.
What causes "REACT_123"?
React library files are corrupted or incomplete in the production build Build process failed to properly bundle or minify React Using an outdated, incompatible, or partially installed version of React
Is the "REACT_123" error serious?
Yes. This is a critical-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading