vscode-ecscript

VS Code extension for ecscript, backed by tree-sitter-ecscript.

Current scope

The extension currently provides:

• registers .ecs as the ecscript language
• installs line/block comments and bracket pairs
• exposes a small status command for smoke-checking activation
• exposes a syntax-tree command for inspecting the parsed CST
• registers a tree-sitter-backed semantic tokens provider

Planned architecture

The long-term goal is to keep the extension thin and reuse the grammar from tree-sitter-ecscript:

1. generate a parser artifact suitable for VS Code loading
2. load the parser from the extension host
3. reuse queries/highlights.scm
4. map tree-sitter captures to VS Code highlighting
5. optionally reuse queries/injections.scm for cmd{ ... }

Why this is separate

This folder is intentionally structured so it can become its own repository later without heavy refactoring.

The intended split is:

• tree-sitter-ecscript/: language grammar, queries, corpus tests
• vscode-ecscript/: VS Code packaging and editor integration

Local development

Install dependencies and build the extension:

cd packages/vscode-ecscript
npm install
npm run build

Or from the monorepo root:

just npm-install
just vscode

Refresh the copied query files and wasm from the grammar package:

just sync-vscode-assets

Then open this folder in VS Code and launch the extension host with the normal extension development workflow.

The current minimum useful checks are:

• Ecscript: Show Extension Status
  • verifies that the extension can load the bundled parser wasm and highlight query
• Ecscript: Show Syntax Tree
  • parses the active .ecs document and opens its syntax tree as an S-expression

The extension currently registers a semantic tokens provider for .ecs files. The first version is intentionally conservative and reuses the synced assets/queries/highlights.scm query plus the generated wasm parser.

Custom keyword colors

The extension defines four custom semantic token types (keywordDeclaration, keywordControl, keywordImport, keywordCommand) so that different keyword classes can be styled independently.

To customize their colors, add this to your settings.json:

"editor.semanticTokenColorCustomizations": {
  "rules": {
    "keywordDeclaration:ecscript": "#C586C0",
    "keywordControl:ecscript":     "#569CD6",
    "keywordImport:ecscript":      "#4EC9B0",
    "keywordCommand:ecscript":     "#D7BA7D",
    "keyword.modifier:ecscript":   "#DCDCAA"
  }
}

Each theme may handle these custom token types differently. If a theme does not provide specific semantic rules, the TextMate fallback scopes defined in package.json (storage.type.ecscript, keyword.control.ecscript, etc.) will be used instead.

Next steps

• consume queries/injections.scm for cmd{ ... } syntax highlighting
• add incremental parsing instead of reparsing the entire document