microsoft / microsoft/vscode-textmate
degradation (latest version) does not support WTF-8+BOM anymore
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 678
- Forks
- 135
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 2
Description
At my workplace we use a custom language for which i made textMate grammar extension for VS Code.
This extension worked perfectly until the november 2025 update. The only change that i could find was a version bump for this textmate dependency.
Of course i might have missed another change, but it wasn't in the release notes at least.
my grammar definition was written in a file encoded using UTF-8+BOM. removing the BOM fixed the plugin, but this is a regression for all non maintained plugins that might be using this file encoding
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the regression with the UTF-8+BOM grammar definition described in the issue, comparing the current behavior with the pre-November 2025 version and its TextMate dependency bump. Trace grammar loading and encoding handling to identify where the BOM is rejected. Done means the grammar loads and tokenizes without requiring users to remove the BOM, with regression coverage for this encoding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100