ESLint: Forbidden non-null assertion (no-non-null-assertion) in a React project
Forbidden non-null assertionShort answer
The rule flags every use of the postfix ! operator because it tells the compiler a value is not null without proving it. Replace the ! with optional chaining and a fallback, or with an explicit check that narrows the type. If a line really needs it, disable the rule for that line only.
Fix it fast
1Find out which cause you have
See which config switches the rule on. The strict preset of typescript-eslint includes it.
grep -rn "no-non-null-assertion\|strict" eslint.config.* .eslintrc* 2>/dev/null2Match what you see, then jump to its fix
What does the error look like?
Forbidden non-null assertion@typescript-eslint/no-non-null-assertion
Cause 1 of 2
The ! operator is used where the value may really be null
1Check
The ! tells TypeScript the value is not null or undefined, but nothing checks it at run time. The TypeScript handbook says the operator does not change runtime behavior.
grep -rn "[a-zA-Z)]!\." src/ | head2Fix
Use optional chaining with a fallback, or check the value and handle the missing case.
// before
const len = user!.name.length;
// after
const len = user?.name.length ?? 0;
// before
const root = document.getElementById('root')!;
// after
const root = document.getElementById('root');
if (!root) throw new Error('Missing #root element');3Verify
The linter passes and the type checker still agrees.
npx eslint src && npx tsc --noEmitConfirmed by typescript-eslint.io
Cause 2 of 2
The project has many assertions and cannot fix them at once
1Check
The rule's documentation advises against turning it off completely, but accepts disable comments for the specific cases while types are being improved.
npx eslint src --format compact | wc -l2Fix
Fix the lines you can, and add a disable comment on each line that must stay, with the reason.
// eslint-disable-next-line @typescript-eslint/no-non-null-assertion -- value set in beforeEach
const store = testStore!;3Verify
The remaining reports are only for lines without a comment.
npx eslint srcConfirmed by typescript-eslint.io
How do I stop it coming back?
- Model optional data as optional in the types and narrow it where it is used.
- Throw one clear error at the edge (for example for #root) instead of asserting everywhere.
- Review any new eslint-disable comment in code review.
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