React warns that rendering a Context directly is not supported
Rendering <Context> directly is not supported and will be removed in a future major releaseShort 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.
Fix it fast
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[ >]" src2Match what you see, then jump to its fix
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-dom2Fix
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@193Verify
The warning is gone from the console and children still receive the value.
npm ls react react-domConfirmed by react.dev
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>" src2Fix
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 browserConfirmed by react.dev
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:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix