ESLint says a JSX component is not defined (react/jsx-no-undef)
'Hello' is not defined react/jsx-no-undefShort 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.
Fix it fast
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.jsx2Match what you see, then jump to its fix
- 1
The name appears in JSX but nowhere else in the fileThe component was never importedFix - 2
The import exists, but the file exports the component the other wayDefault and named imports are mixed upFix - 3
The component is defined by a script or config outside the fileThe component is meant to be a globalFix
- 1
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.jsx2Fix
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.jsxConfirmed by github.com
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.jsx2Fix
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
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.jsxConfirmed by github.com
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:
- 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
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix