Syntax highlighting breaks when anything is after {}

[KianNH]

Initial checklist

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

Affected packages and versions

unifiedjs.vscode-mdx v1.8.10

Link to runnable example

No response

Steps to reproduce

Paste the following snippets into separate MDX files:

{props.name}

```js
export const foo = "bar";
```

[foo](/bar/)

{props.name} a

```js
export const foo = "bar";
```

[foo](/bar/)

It looks like this can also be reproduced with GitHub's highlighting, so maybe it's an issue with the grammar?

Expected behavior

Both should have the same syntax highlighting.

Actual behavior

The second one, with a character after the brackets, has broken syntax highlighting.

Runtime

Node v21

Package manager

No response

OS

No response

Build and bundle tools

No response

[wooorm]

Thanks! I think I have it.

[sebas1208]

I found a probably related issue with code blocks inside JSX components.

the closing tag is still recognized as ruby code.

[remcohaszing]

I found a probably related issue with code blocks inside JSX components.

That was a duplicate of #472, which was already resolved, but not yet released.