Describe the problem

Similar to #834

I ran into an issue today that react-x/no-unknown-property is not implemented in eslint-plugin-react-x, as noted in #85:

The following can be enforced by TypeScript, no need to implement them

• react/no-unknown-property

This causes problems for environments where TypeScript is not available

Eg. there is not yet full TypeScript support for MDX files, and it appears ESLint doesn't support multiple parsers for a set of files (eg. for trying to use typescript-eslint parser along with the MDX parser).

Describe the solution you'd like

It would be great to get react-x/no-unknown-property implemented for other languages like MDX? (and also just for completeness, for other situations where TypeScript cannot be used)

Alternatives considered

Keep using react/no-unknown-property via eslint-plugin-react

Additional context

Ideally, this rule would be implemented also with abilities to extend for other environments like React Three Fiber (a missing feature of react/no-unknown-property):

• [react/no-unknown-property] rule conflicts with @react-three/fiber on <mesh /> and other tags jsx-eslint/eslint-plugin-react#3423