Cannot use props as function-local variables

[PaulRBerg]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and discussions and couldn’t find anything (or linked relevant results below)

Affected package

eslint-plugin-mdx@3.1.5

Steps to reproduce

Suppose you have some code like this:

### {props.foo}

{props.foo} is a foo.

### {props.bar}

{props.bar} is a bar.

Actual behavior

ESLint will throw the following errors:

  1:6  error  'props' is not defined  no-undef
  3:2  error  'props' is not defined  no-undef
  5:6  error  'props' is not defined  no-undef
  7:2  error  'props' is not defined  no-undef

Expected behavior

The code should compile just fine or there should be a way to let ESLint know that those are props

Note: I've asked this question here, and @remcohaszing suggested that this might be a bug.

Runtime

node v22.14.0

Package manager

bun

Operating system

macOS@15.3.2

Build and bundle tools

Docusaurus

[JounQin]

Welcome, @PaulRBerg! Thanks for reporting this issue.

PR welcome to add props: false after

eslint-mdx/packages/eslint-plugin-mdx/src/configs/overrides.ts

Line 18 in 870a3a6

React: false,

and

eslint-mdx/packages/eslint-plugin-mdx/src/configs/flat.ts

Line 16 in 870a3a6

React: false,

[remcohaszing]

Note that props is not available in mdxjsEsm nodes. It’s only allowed in MDX content. But I do agree with @JounQin’s solution, at least as temporary solution. It’s better to have a false negative than a false positive.

[JounQin]

Note that props is not available in mdxjsEsm nodes. It’s only allowed in MDX content. But I do agree with @JounQin’s solution, at least as temporary solution. It’s better to have a false negative than a false positive.

Oh, indeed, export const foo = props.bar should not work, totally forgot about this case, I'll try to find a better solution when I'm free.