Polyglot for VS Code
Language support for Polyglot (.pg) — one small source language that transpiles to idiomatic,
readable C#, TypeScript, Python, and PHP.
Features
- Syntax highlighting for
.pg files (TextMate grammar).
- Language server (spawned as
polyglot lsp): live diagnostics, go-to-definition (including into
the std library), hover, document symbols, semantic tokens, formatting, references, rename, and
completion (including obj. members).
- Live generated-output preview — Show Generated Output opens the emitted C#, TypeScript, and
Python beside your
.pg file and updates as you type. A Polyglot Outputs explorer view opens a
single target on demand.
- Per-target reserved-name checks — identifiers that would collide with a configured target's
generated code or runtime globals squiggle live, named per target.
Requirements
Everything except syntax highlighting needs the polyglot CLI, which hosts the language server:
- If
polyglot is on your PATH, it is picked up automatically.
- Otherwise set
polyglot.cliPath to the executable (a relative path resolves against the
workspace root).
Project configuration
An optional pgconfig.json next to (or above) your .pg files drives module resolution and the
target set:
{
"root": ".",
"lib": ["io", "math"],
"targets": ["csharp", "typescript"]
}
root is the base for logical imports (import { a } from "geometry"), lib is the ambient std
prelude, targets is the project's target set (drives polyglot build and the per-target
reserved-name squiggles). forbiddenIdentifiers can ban names project-wide or per target.
Settings
| Setting |
Default |
Description |
polyglot.cliPath |
polyglot |
Path to the polyglot CLI (which hosts the language server). |
polyglot.lib |
io,math |
Fallback std prelude when no pgconfig.json is found. |
polyglot.trace.server |
off |
Trace the JSON-RPC traffic (for debugging the server). |
Learn the language
