microsoft / microsoft/TypeScript-TmLanguage
"import" is highlighted as a keyword in Node.js "import.meta.dirname" expression
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 471
- Forks
- 149
- PR merge metrics
- No merged PRs in 30d
Description
JavaScript and TypeScript Nightly version: 6.0.20260416
Code
import path from "naode:path";
import.meta.dirname;
Issue
In "textmate scopes" section the "keyword.control.import.js" token is shown.
But this "import" word is not a "keyword".
Steps to reproduce
- Open
.jsfile - Write
import.meta.dirname - Click "import" word
- Press "Ctrl+Shift+P" type and select "Developer: Inspect Editor Tokens and Scopes"
🖼️ Screenshot
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
Reproduce the issue in a .js file with import.meta.dirname, then use Developer: Inspect Editor Tokens and Scopes on import. Trace the TypeScript TextMate grammar rule producing keyword.control.import.js; done means this expression no longer assigns that keyword scope to import while regular imports remain correctly highlighted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100