Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Syntax Highlighting Breaks with Frontmatter #462

Closed
4 tasks done
Lakuna opened this issue Aug 3, 2024 · 4 comments
Closed
4 tasks done

Syntax Highlighting Breaks with Frontmatter #462

Lakuna opened this issue Aug 3, 2024 · 4 comments
Labels
👀 no/external This makes more sense somewhere else 👎 phase/no Post cannot or will not be acted on

Comments

@Lakuna
Copy link

Lakuna commented Aug 3, 2024

Initial checklist

Affected packages and versions

MDX v1.8.9

Link to runnable example

No response

Steps to reproduce

As of today (potentially related to the new Visual Studio Code update 1.92, which came out yesterday), MDX files with frontmatter don't display proper syntax highlighting.

  1. Create a file and use MDX syntax highlighting.
  2. Add frontmatter to the file.
  3. Write standard MDX content below the frontmatter.

I am using Node.js version 22.3.0.

Expected behavior

The standard syntax highlighting should appear (this was the case for me until today).

image

Actual behavior

The entire file is highlighted as if it were YAML.

image

Runtime

Other (please specify in steps to reproduce)

Package manager

npm v10

OS

Windows

Build and bundle tools

Next.js

@github-actions github-actions bot added 👋 phase/new Post is being triaged automatically 🤞 phase/open Post is being triaged manually and removed 👋 phase/new Post is being triaged automatically labels Aug 3, 2024
@remcohaszing
Copy link
Member

Duplicate of wooorm/markdown-tm-language#10

@remcohaszing remcohaszing closed this as not planned Won't fix, can't repro, duplicate, stale Aug 3, 2024

This comment has been minimized.

@remcohaszing remcohaszing added the 👀 no/external This makes more sense somewhere else label Aug 3, 2024

This comment was marked as resolved.

@github-actions github-actions bot added 👎 phase/no Post cannot or will not be acted on and removed 🤞 phase/open Post is being triaged manually labels Aug 3, 2024
@remcohaszing
Copy link
Member

remcohaszing commented Aug 3, 2024

But it is interesting to know this was caused by VSCode 1.92.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👀 no/external This makes more sense somewhere else 👎 phase/no Post cannot or will not be acted on
Development

No branches or pull requests

2 participants