TypeScript rejects a value passed to a useState setter
Type 'number' is not assignable to type 'SetStateAction<undefined>'.Short answer
useState gets its type from the initial value. Starting with useState(undefined) or useState(null) types the state as only undefined or null, so the setter refuses a number. Give useState an explicit union type, such as useState<number | null>(null). The same error appears when a component such as Mantine Select hands your setter a string or null.
Fix it fast
1Find out which cause you have
Hover the state variable in your editor, or ask the compiler what type it inferred. If it says undefined or null alone, the cause is the initial value. If it says number but the value passed in is string | null, the cause is the component.
npx tsc --noEmit2Match what you see, then jump to its fix
What does the error look like?
Type 'number' is not assignable to type 'SetStateAction<undefined>'.
Cause 1 of 2
The initial value is undefined, so the state type is only undefined
1Check
React infers the state type from the initial value. useState(undefined) therefore gives a state that can only hold undefined, and its setter accepts only undefined or an updater function that returns undefined.
grep -rn "useState(undefined)\|useState()" src/2Fix
Name the type you want with a type argument, and include undefined or null for the empty state.
const [count, setCount] = useState<number | undefined>(undefined);
setCount(5);3Verify
Run the type check; the error is gone and the editor shows number | undefined.
npx tsc --noEmitConfirmed by react.dev
Cause 2 of 2
A Mantine Select gives your setter string | null, not number
1Check
The Mantine Select documents its controlled value as string | null; the controlled example types the state as string | null. A number state does not match.
grep -rn "<Select" src/2Fix
Keep the state as the select's type, and convert where you need a number.
const [value, setValue] = useState<string | null>(null);
const quantity = value === null ? undefined : Number(value);
<Select data={['1', '2', '3']} value={value} onChange={setValue} />3Verify
Run the type check, then pick an option and confirm quantity is a number.
npx tsc --noEmitConfirmed by mantine.dev
How do I stop it coming back?
- Give every useState with an empty start an explicit type argument.
- Check a component's documented value type before you wire your own state to it.
- Run tsc --noEmit in CI so type errors show before a build.
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