Bug: Ampersand breaks jsx_text

[Jeaciaz]

The following piece of code is valid but it is parsed incorrectly:

export const a = <div>me & you</div>

Here's a link to the TypeScript Playground showing that the snippet above is valid JavaScript or TypeScript:
https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAJQKYEMDG8BmUIjgcilQ3wG4AocpAD0ljjQgDsBneFOAXjgB4ATYADcAfCCRwAZHACeEAK48A9AJFA

I unfortunately couldn't get the CLI to find installed languages (if absolutely required, they are located in ~/.local/share/nvim/lazy/nvim-treesitter; if someone could help me find what I need to add to ~/.config/tree-sitter/config.json, I can absolutely do that). However, nvim's :InspectTree could hopefully be enough to paint the picture:

There was a very similar issue with ampersands in jsx attributes - it was remedied, however the jsx_text node is still broken.

Also if the ampersand if a part of an html entity, the parser works as expected:

[JOSEFT404]

Thanks for the detailed repro — this looks like a grammar boundary issue specific to jsx_text.

Since & behaves correctly when parsed as an entity but not as raw text (and attributes were fixed previously), it suggests the JSX text/operator boundary is only partially enforced.

I believe this can be clarified with a short correctness analysis outlining why the entity path succeeds while raw text fails, and what invariant is currently violated.

Before writing that up, could you confirm whether a scoped analysis like this would be handled as a funded contribution via Open Collective?