Skip to content
← Back to rules

react/jsx-no-undef Correctness

What it does ​

Disallow undeclared variables in JSX.

Note that this rule is generally unnecessary if you are using TypeScript, as TypeScript will catch undeclared variables for you.

Why is this bad? ​

It is most likely a potential ReferenceError caused by a misspelling of a variable or parameter name.

Examples ​

Examples of incorrect code for this rule:

jsx
const A = () => <App />;
const C = <B />;

How to use ​

To enable this rule using the config file or in the CLI, you can use:

json
{
  "plugins": ["react"],
  "rules": {
    "react/jsx-no-undef": "error"
  }
}
ts
import { defineConfig } from "oxlint";

export default defineConfig({
  plugins: ["react"],
  rules: {
    "react/jsx-no-undef": "error",
  },
});
bash
oxlint --deny react/jsx-no-undef --react-plugin

Version ​

This rule was added in v0.1.1.

References ​