createRoot fails with Target container is not a DOM element
Error: Target container is not a DOM element.Short answer
createRoot needs a real DOM node. If the argument is null or a React element, React throws this error. Log the value you pass in. A null result means getElementById found nothing: the id differs, or your script runs before the element exists in the HTML. A component passed in place of the node is the other cause.
Fix it fast
1Find out which cause you have
Print the value passed to createRoot. null means no element was found; anything else means it is not a node.
const domNode = document.getElementById('root'); console.log(domNode); const root = createRoot(domNode);2Match what you see, then jump to its fix
What does the error look like?
Error: Target container is not a DOM element.Uncaught Error: Target container is not a DOM element
Cause 1 of 3
The id in the code differs from the id in the HTML
1Check
Compare the id string in getElementById with the id attribute in your HTML file or template, letter by letter.
grep -rn "id=\"root\"\|getElementById" public src index.html2Fix
Make the two match.
<div id="root"></div>
const domNode = document.getElementById('root');3Verify
Reload; the console should now print the element, not null.
console.log(document.getElementById('root'))Confirmed by react.dev
Cause 2 of 3
The script runs before the element is in the page
1Check
A script cannot see nodes that come after its tag in the HTML. Check where the bundle's script tag sits compared with the root div. This often happens in Django or other server templates.
grep -n "<script\|id=\"root\"" templates/index.html2Fix
Put the script tag after the root element, at the end of the body.
<body>
<div id="root"></div>
<script src="/static/bundle.js"></script>
</body>3Verify
Reload the page and check the console.
console.log(document.getElementById('root'))Confirmed by react.dev
Cause 3 of 3
A component was passed instead of the node
1Check
Look at the createRoot call. The component belongs in render, not in createRoot.
grep -rn "createRoot(" src2Fix
Pass the DOM node to createRoot and the component to render.
const root = createRoot(document.getElementById('root'));
root.render(<App />);3Verify
Reload the page.
npm startConfirmed by react.dev
How do I stop it coming back?
- Keep the root id in one place and reuse it in the template and the entry file.
- Load the bundle at the end of the body, or use a script tag with defer.
- Render a different root div per React app when one page holds several.
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