Make JSX/TSX a plugin, to prove out custom parser support.

[NullVoxPopuli]

pls don't build in JSX/TSX

The first linter / parser that has generic language supports wins everyone <3

We have:

script in html (clearly defined markers)

• vue
• svelte

html in script (clearly defined markers)

• angular (sorta)
• ember

hard mode (interwoven everywhere)

• jsx

* in markdown

• mdx
• astro
• other docs tools

eslint allows the smooshing of nested ASTs, which means lint rules can span both JS and <nested language> -- it's very nice. I've yet to see any of the new linters get to this level of flexibility

[fansenze]

Thanks for raising this! We agree that extensible language support is important, especially for mixed-language syntax such as JSX/TSX.

Rslint’s direction is to support more languages natively to deliver the best possible lint performance. For those languages, JavaScript rule plugins should be able to consume and traverse the AST exposed by the corresponding native implementation, including both JavaScript and language-specific nodes.

At the same time, we want users to be able to bring custom language support through ESLint-compatible JavaScript language/parser plugins, in the same way they do with ESLint.

This combines native performance for first-party languages with the rule ecosystem and language extensibility of ESLint. The exact API and integration details still need to be designed, but this is the direction we have in mind.