Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

React warns that rendering a Context directly is not supported

ErrorRendering <Context> directly is not supported and will be removed in a future major release

Short answer

The warning means you wrote JSX with the Context object itself, such as <ThemeContext value={x}>. React 19 accepts that as a provider. React 18 does not. Use <ThemeContext.Provider> on 18, upgrade to 19, and read values with useContext instead of the Context tag.

  • Applies to React 18.3, React 19
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Check which React version the app really resolves, then search for JSX that uses a context name with no .Provider or .Consumer.

    npm ls react
    grep -rnE "<[A-Za-z]+Context[ >]" src
  2. 2Match what you see, then jump to its fix

    1. 1npm ls react shows 18.x, and the code has <SomeContext value={...}>.React 19 provider syntax is running on React 18Fix
    2. 2The code has <SomeContext> with a function child, or with no value prop at all.The Context was used to read a value, not to provide oneFix

What does the error look like?

  • Rendering <Context> directly is not supported and will be removed in a future major release

Cause 1 of 2

React 19 provider syntax is running on React 18

1Check

React's createContext page says that starting in React 19 you can render <SomeContext> as a provider; older versions use <SomeContext.Provider>.

npm ls react react-dom

2Fix

On React 18 write the provider with .Provider, or upgrade React and react-dom together.

<ThemeContext.Provider value={theme}>
  <Page />
</ThemeContext.Provider>

# or upgrade:
npm install react@19 react-dom@19

3Verify

The warning is gone from the console and children still receive the value.

npm ls react react-dom

Confirmed by react.dev

Did this fix it?

Cause 2 of 2

The Context was used to read a value, not to provide one

1Check

To read context, the docs recommend useContext. SomeContext.Consumer, which takes a function as its child, is the rarely used legacy way.

grep -rn "Context>" src

2Fix

Call useContext in the component that needs the value.

function Button() {
  const theme = useContext(ThemeContext);
  return <button className={theme} />;
}

3Verify

The component shows the value from the nearest provider.

# manual check in the browser

Confirmed by react.dev

Did this fix it?

How do I stop it coming back?

  • Pin react and react-dom to the same major version in package.json.
  • Read context with useContext in new code.
  • When you copy provider code from a React 19 example, check your own React version first.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.