TypeScript: Cannot assign to current because it is a read-only property
Cannot assign to 'current' because it is a read-only propertyShort answer
With React 18 types, useRef(null) returns a ref whose current cannot be assigned. That type exists for DOM refs, not for mutable values. Add | null to the generic, give a real initial value, or upgrade to React 19 types, where every ref is mutable.
Fix it fast
1Find out which cause you have
Check which @types/react version is installed: the behaviour differs between 18 and 19.
npm ls @types/react react2Match what you see, then jump to its fix
What does the error look like?
Cannot assign to 'current' because it is a read-only property
Cause 1 of 2
useRef<T>(null) returns a read-only RefObject under the React 18 types
1Check
In the 18 types, an argument of type T | null returns RefObject<T>, whose current is readonly. A ref given as the ref prop of an element is meant to be written by React, not by you.
grep -rn "useRef<" src/2Fix
Include | null in the generic argument so the ref is directly mutable. Or pass an initial value of type T.
const timer = useRef<number | null>(null);
timer.current = 1;3Verify
Run the type check.
npx tsc --noEmitConfirmed by raw.githubusercontent.com
Cause 2 of 2
Your project is on the React 18 types, and the React 19 types would fix it
1Check
In the React 19 types all refs are mutable and a single RefObject type is returned by useRef. useRef also now requires an argument.
npm ls @types/react2Fix
Upgrade React and its types together, following the upgrade guide.
npm install react@19 react-dom@19 && npm install --save-dev @types/react@19 @types/react-dom@193Verify
Run the type check.
npx tsc --noEmitConfirmed by react.dev
How do I stop it coming back?
- Use useRef<HTMLInputElement>(null) for DOM refs and let React write to current.
- For values you write yourself, include | null (or a real initial value) in the type.
- Upgrade React and @types/react in the same commit.
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