Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

ESLint says a JSX component is not defined (react/jsx-no-undef)

Error'Hello' is not defined react/jsx-no-undef

Short answer

The rule flags a component used in JSX that is not declared in that file. The usual cause is a missing import. Next check that a named import uses braces and the exact name, and a default import does not. If the component really is a global, set the rule's allowGlobals option.

  • Applies to eslint-plugin-react 7, ESLint 9, React 19
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Run the linter on the one file and read the line number. Then look at the top of that file for an import with the same name.

    npx eslint src/App.jsx
  2. 2Match what you see, then jump to its fix

    1. 1The name appears in JSX but nowhere else in the fileThe component was never importedFix
    2. 2The import exists, but the file exports the component the other wayDefault and named imports are mixed upFix
    3. 3The component is defined by a script or config outside the fileThe component is meant to be a globalFix

What does the error look like?

  • 'Hello' is not defined react/jsx-no-undef

Cause 1 of 3

The component was never imported

1Check

The rule helps find ReferenceErrors from misspellings or missing components. Search the file for the name.

grep -n "Hello" src/App.jsx

2Fix

Import the component from its file with a relative path.

import Hello from './Hello';

export default function App() {
  return <Hello name="John" />;
}

3Verify

Run ESLint again; the error is gone.

npx eslint src/App.jsx

Confirmed by github.com

Did this fix it?

Cause 2 of 3

Default and named imports are mixed up

1Check

A default import takes any name without braces; a named import needs braces and the same name as the export. Using one form for the other gives an error.

grep -n "export" src/Hello.jsx

2Fix

Match the import to the export.

// Hello.jsx: export function Hello() {}
import { Hello } from './Hello';

// Hello.jsx: export default function Hello() {}
import Hello from './Hello';

3Verify

ESLint passes and the component renders.

npx eslint src/

Confirmed by react.dev

Did this fix it?

Cause 3 of 3

The component is meant to be a global

1Check

By default the rule ignores the global scope when checking for defined components.

grep -n "jsx-no-undef" eslint.config.js .eslintrc*

2Fix

Turn on allowGlobals so the rule considers the global scope.

"react/jsx-no-undef": ["error", { "allowGlobals": true }]

3Verify

Run ESLint and confirm the warning is gone for that component.

npx eslint src/App.jsx

Confirmed by github.com

Did this fix it?

How do I stop it coming back?

  • Let the editor add imports for you with its auto-import action.
  • Use one export style per project (all default or all named).
  • Run ESLint before each commit so a missing import never reaches the 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:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.