TypeScript says property children is missing in type when you render a React component
Property 'children' is missing in typeShort answer
TypeScript is telling you the component's props type lists children as required, and this call site gives none. Either put content between the tags, or make children optional in the type. If strings and numbers fail to type-check, the prop is typed as ReactElement; use ReactNode.
Fix it fast
1Find out which cause you have
Read the props type of the component named in the error, and look for a children line without a question mark.
grep -rn "children" src/components/Modal.tsx2Match what you see, then jump to its fix
- 1
Property 'children' is missing in type '{ title: string; }' for a self-closing tag such as <Modal title="x" />.children is declared as required, and the component is used without contentFix - 2
A type error appears only when the child is a string, number or fragment.children is typed as ReactElement, but text or numbers are passedFix
- 1
What does the error look like?
Property 'children' is missing in type
Cause 1 of 2
children is declared as required, and the component is used without content
1Check
In the props interface, children has no question mark, so every use must pass it.
grep -n "children" src/components/Modal.tsx2Fix
Wrap content in the tags at the call site. If the component works fine without children, mark the property optional with a question mark.
interface ModalProps {
title: string;
children?: React.ReactNode;
}3Verify
Run the type check.
npx tsc --noEmitConfirmed by typescriptlang.org
Cause 2 of 2
children is typed as ReactElement, but text or numbers are passed
1Check
ReactElement only accepts JSX elements, not primitives such as strings or numbers.
grep -rn "ReactElement" src/2Fix
Use ReactNode, the union of everything that can be passed as children.
interface ModalProps {
title: string;
children: React.ReactNode;
}3Verify
Run the type check.
npx tsc --noEmitConfirmed by react.dev
How do I stop it coming back?
- Type children as React.ReactNode unless you need only JSX elements.
- Decide for each wrapper component if empty content is allowed, and encode that with or without the question mark.
- Run tsc --noEmit in CI so type errors do not wait for a release.
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
TypeScript refuses JSX because the jsx option is not set
TS17004: Cannot use JSX unless the '--jsx' flag is provided.
TypeScript compiles JSX only when you name the file with a .tsx extension and enable the jsx compiler option.
2 causes, each with a fixWeb apps
TypeScript rejects a component that returns an array or other non-Element
Its return type 'Element[]' is not a valid JSX element.
TypeScript before 5.1 required every component to return JSX.Element or null, so arrays, strings and Promises were rejected even though React renders them.
2 causes, each with a fixWeb apps
ESLint says it cannot resolve a path to a module that does exist
Unable to resolve path to module 'react'. import/no-unresolved
import/no-unresolved fails when eslint-plugin-import cannot find the file or package on disk with its resolver.
4 causes, each with a fixWeb apps
ESLint reports no-unused-vars for React components and imports that are used
no-unused-vars reported for a component that is rendered as a JSX tag
ESLint's core no-unused-vars does not see variables used only as JSX tags, so a component imported and rendered as <Hello /> looks unused.
3 causes, each with a fixWeb apps
TypeScript rejects MUI Data Grid columns that set a type
A TypeScript error inside a column's renderCell callback
A columns array declared without a type is inferred with type as a plain string, which the Data Grid's column type union does not accept.
2 causes, each with a fixWeb apps
The renderInput prop stopped working on the MUI X DatePicker
The custom TextField (variant, size, helperText) is ignored
renderInput was removed from the MUI X date pickers in version 6.
3 causes, each with a fix