Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>Editor Lang ToolkitNew to Visual Studio Code? Get it now.
Editor Lang Toolkit

Editor Lang Toolkit

HeavenSky

|
82 installs
| (0) | Free
Schema validation, completion and formatting for YAML and TOML, real terminal colours for ANSI logs, and F5 debugging for uv Python projects, with no language server or CLI to install.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Editor Lang Toolkit

English · 简体中文

Schema validation, completion and formatting for YAML and TOML, real terminal colours for ANSI logs, and F5 debugging for uv Python projects, with no language server or CLI to install.

VS Marketplace Installs License

VS Code ships a full language service for JSON, but only a syntax grammar for YAML and nothing at all for TOML. Extensions that fill the gap often ask you to install a CLI such as taplo first. This one bundles both language servers, so opening a config file is all it takes. There is no telemetry.

A YAML file checked against its JSON Schema: "replicas: three" is flagged as "Incorrect type. Expected integer"

Get started

  1. Install the extension:

    code --install-extension HeavenSky.editor-lang-toolkit
    
  2. Open a well-known YAML file, such as a GitHub workflow: mistakes are underlined right away.

  3. For any other YAML file, add a schema on the first line, then press Ctrl+Space for completions:

    # yaml-language-server: $schema=./service.schema.json
    

Catch config mistakes as you type

YAML and TOML files are validated against JSON Schema while you edit, and the same schema drives completion and hover. YAML picks the schema from a modeline, an inline $schema, the yaml.schemas setting or the SchemaStore catalog; TOML reads its associations from .taplo.toml. See Validate YAML and TOML against a schema for the full rules.

Completion in a YAML file, with values and descriptions taken from its JSON Schema

Share one TOML config between the editor and CI

The extension reads the same .taplo.toml as the taplo CLI, so formatting and schema rules match in both places without a second copy. Without that file, the langToolkit.taplo setting carries the same options.

A TOML file with syntax highlighting and a schema error

Read terminal logs in their real colours

Files with the ansi language (.ans, .ansi) are shown with their escape codes rendered as colours, from the 16 basic colours to 24-bit true colour. Colours come from your theme's terminal palette, so there is nothing to configure. To colour other files, such as logs:

{ "files.associations": { "*.log": "ansi" } }

An ANSI log rendered in colour, next to a preview with the escape codes removed

Debug a uv project with F5

Press F5 in a .py file to debug it with breakpoints, stepping and variables, without the Microsoft Python extensions; you only need uv installed. The program runs in the environment uv run resolves for your project, and debugpy is fetched by uv on the fly, never added to your project. Debug Python in a uv project covers launch.json templates and attaching.

When not to use it

The Python support is a debugger only: if you want an interpreter picker, a test explorer or notebooks, use the Microsoft Python extension. If you need TOML formatting or validation outside the editor, run the taplo CLI against the same .taplo.toml; this extension does not ship a command-line tool.

Learn more

The guides cover schemas, ANSI files, Python debugging, network access and troubleshooting. Commands and settings are listed on the marketplace page's Feature Contributions tab. See the changelog for what changed in each release, and NOTICE.md for the upstream projects this extension bundles.

License

MIT

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft