React warns that a div sits directly inside a tbody
Warning: validateDOMNesting(...): <div> cannot appear as a child of <tbody>.Short answer
HTML only lets a tbody contain tr elements, plus script-supporting elements. A div directly inside it is invalid, so React warns. Put a tr there, and put the content in a td. For a message that spans the whole table, use one td with colSpan. Check wrapper components that render a div inside table markup.
Fix it fast
1Find out which cause you have
The warning prints a component stack. Read it from the top to find the component that renders the div, then open that file.
grep -rn "<tbody" src/2Match what you see, then jump to its fix
What does the error look like?
Warning: validateDOMNesting(...): <div> cannot appear as a child of <tbody>.
Cause 1 of 2
A div is written directly inside tbody
1Check
The HTML specification gives the content model of tbody as zero or more tr elements and script-supporting elements. A div is neither.
grep -rn -A2 "<tbody" src/ | grep "<div"2Fix
Return rows, and put the content into cells.
<tbody>
{items.map(item => (
<tr key={item.id}>
<td>{item.name}</td>
</tr>
))}
</tbody>3Verify
Reload the page and check that the console warning is gone.
# browser console: no validateDOMNesting messageConfirmed by html.spec.whatwg.org
Cause 2 of 2
A component renders a div, such as an empty-state or loading message
1Check
A custom component can hide the div. A td may sit only directly inside a tr, and tr may hold td, th and script-supporting elements, so a message must be a row with a cell.
grep -rn "No data\|Loading" src/ | head2Fix
Render a row with one cell that spans all columns, using colSpan.
<tbody>
<tr>
<td colSpan={4}>No results found.</td>
</tr>
</tbody>3Verify
Show the empty state and check that the console is clean.
# browser console: no validateDOMNesting messageConfirmed by html.spec.whatwg.org
How do I stop it coming back?
- Treat table, thead, tbody and tr as fixed structure: only rows in tbody, only cells in tr.
- Keep a wrapper div outside the table, not inside it.
- Open the console after changing a table component.
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