YoptaScript for VS Code

Language support for YoptaScript — an esoteric language with Russian slang keywords, implemented in Rust.

Installation

Install from the VS Code Marketplace: search for "YoptaScript" in the Extensions view, or run

code --install-extension ixxydev.yoptascript

Features

Syntax highlighting for .yopta files via a TextMate grammar (keywords, strings, template literals, numbers, comments, constants and operators).
Language server features backed by yps-lsp:
- live diagnostics (lexer + parser errors)
- hover docs for keywords
- completion (keywords, builtins and declarations from the current file)
- document outline / breadcrumbs (textDocument/documentSymbol)
- formatting (textDocument/formatting, powered by yps-fmt)
- go-to-definition (textDocument/definition)
Debugger backed by yps-dap (Debug Adapter Protocol over the tree-walking interpreter): breakpoints, step over/in/out, pause, call stack, local variables, сказать output in the Debug Console.

Debugging

Open a .yopta file and press F5 — no launch.json needed (the extension debugs the active file). For a persistent setup, add a configuration:

{
  "type": "yoptascript",
  "request": "launch",
  "name": "Отладка YoptaScript",
  "program": "${file}",
  "stopOnEntry": false
}

The yps-dap binary is resolved the same way as the language server: the yoptascript.dap.path setting first, then a bundled bin/<platform>-<arch>/yps-dap, then PATH (build one with cargo build --release -p yps-dap).

Known limitations:

Variables are rendered flat (objects/arrays/maps have no expandable children).
Only the innermost stack frame shows locals; outer frames report an empty scope.
Stepping granularity is one statement, not one expression.
Breakpoints are accepted only in the launched file; breakpoints set in any other file (including imported modules) show up as unverified.
прочестьСтроку/прочестьВсё raise a catchable error under the debugger: the adapter's stdin carries the DAP protocol stream itself.
Uncaught errors inside timer/promise callbacks go to the adapter's stderr and don't reach the Debug Console.

Requirements

The extension is a thin client for the yps-lsp language server. On activation it looks for a server binary in this order:

yoptascript.server.path setting, if set — an explicit path you give it.
Bundled binary — a yps-lsp executable shipped inside the extension itself, at bin/<platform>-<arch>/yps-lsp (e.g. bin/darwin-arm64/yps-lsp, bin/win32-x64/yps-lsp.exe). Marketplace builds packaged with npm run package:local include this; a bare npm run package does not.
PATH — a yps-lsp (or yps-lsp.exe on Windows) executable found on your system PATH.

If none of these resolve to a real file, the extension shows an error message instead of starting (no crash, no restart loop) and tells you how to fix it:

cargo build --release -p yps-lsp

Then either put the binary on PATH, or point the extension at it directly:

{
  "yoptascript.server.path": "/path/to/yoptascript-rs/target/release/yps-lsp"
}

Settings

| Setting | Default | Description | | --- | --- | --- | | yoptascript.server.path | (empty) | Explicit path to the `yps-lsp` executable. Leave empty to use the bundled binary (if present) or search `PATH`. | | `yoptascript.dap.path` | (empty) | Explicit path to the yps-dap debug adapter. Same fallback order as the language server. | | yoptascript.trace.server | off | Trace LSP traffic (off / messages / verbose). |

Building the extension

cd editors/vscode
npm ci
npm run compile      # bundle src/extension.ts -> dist/extension.js with esbuild
npm test             # tokenization + server-resolution tests
npm run package      # produce a .vsix without bundled binaries (requires @vscode/vsce)
npm run package:local # cargo build the yps-lsp + yps-dap release binaries, bundle them under bin/, then package a .vsix

License

MIT OR Apache-2.0

YoptaScript

IxxyDev