[tomaszbk]

Prepare 0.3.0 with managed V/VLS installation and updates, current VLS compatibility, reliable language-server recovery, and formatting and syntax fixes. Requires VS Code 1.140.0 or newer.

Changes

• VLS compatibility: requires VLS 0.0.3 or newer, as reported by vls --version, for external and managed servers alike. Older or unidentified servers offer V: Install or Update VLS.
• Managed V and VLS: builds official sources in isolated, cancellable builds and verifies them before use. The selection is stored per machine, so Settings Sync never shares local paths. An update deletes the build it replaces; other windows still using it ask to reload.
• Updates: at most daily checks against V master or its latest release (v.tools.updateChannel); VLS tracks master.
• Language server: serialized restarts, crash recovery, status and logs. Settings from the former VLS extension keep working.
• Formatting: formats unsaved buffers through stdin, independently of VLS.
• Fixes and tooling: optimized builds through tasks, bounded numeric highlighting, an SVG V file icon, and TypeScript 7 with type-aware Oxlint/Oxfmt.

Upstream integration

Incorporates the dependency update merged in #568, including engines.vscode: ^1.140.0 and @types/vscode: 1.140.0, while retaining extension version 0.3.0 and the migration to Oxc. The resolved manifest uses Oxlint 1.87.0, Oxfmt 0.72.0, TypeScript 7.0.2, and the latest Node 24 API types (24.19.1). Shared runtime/build dependencies remain at the current stable versions: languageclient 10.1.2, vsce 4.0.0, esbuild 0.28.2, and markdownlint-cli 0.49.1.

Dependency

Requires vlang/vls#537, which adds vls --version (VLS 0.0.3). Until it is merged, CI builds VLS from commit e61d428.

Issue scope

• Fixes installV() deletes the entire ~/.local/bin before cloning V #555: managed installation preserves shared directories.
• Fixes Number patterns backtrack exponentially on long digit runs (constant.numeric.float.v, .exponential.v) #553: numeric highlighting avoids exponential backtracking.
• Fixes Functionality to update vls if update is available #190: working VLS update checks and installation.
• Fixes missing commands and filetype icon #372: fallback V file icons and independent command registration.
• Fixes v.fmt not working #523: format-on-save and manual formatting without VLS.
• Closes main() function not showed in outline panel. #537: real-server outline regression includes main.
• Closes Plugin problem on linux #416: automatic recovery restores language features after a crash.
• Supersedes fix: show icons for V files #548 through the SVG icon.
• Related Folding or Colapse imports, structs, enums and fns. #403: imports, structs, enums and functions fold with upstream VLS. Grouped constants still require a server change and are not claimed solved.

Validation

The current integration was verified locally on macOS arm64 with Node 26.6.0, VS Code 1.140.0, V 01eb669, and VLS e61d428:

• Clean locked dependency installation, npm test (111 logic/adapter tests, TypeScript, Oxlint, and Oxfmt checks), all 14 grammar fixtures, README lint, Actionlint, and VSIX packaging pass.
• Installed-VSIX fixture-host tests pass, including tasks, unsaved-buffer formatting, LSP wiring, restarts, crash recovery, rejection of VLS 0.0.2, and issue v.fmt not working #523 with VLS missing.
• Real-VLS host tests pass: completion, hover, definition, three-file rename, collision refusal, formatting, auto-imports, inlay hints, outline, and supported folding. Completed host logs contain no failed configuration or document notifications.
• Windows and Linux runtime checks were not rerun for this integration. CI remains configured for Node 24 and Linux/macOS extension hosts.
• npm audit reports five pre-existing low/moderate development-tool advisories through markdownlint-cli; no high or critical advisories. Its KaTeX and smol-toml versions are unchanged by this integration.

[metif12]

Noticed the overlap with two of my PRs and would rather ask than pile on.

I opened #556 and
#557 against master a few hours
ago, before I found this one. Both are superseded by what is here, and I can
close them:

#556 — installV deleted ~/.local/bin outright before cloning, because the
directory was treated as though it only ever held V:

const userBinPath = path.join(os.homedir(), ".local", "bin")
// ...
if (fs.existsSync(installDir)) {
    fs.rmSync(installDir, { recursive: true, force: true })
}

That is the same defect as the #555 you list, and this PR fixes it structurally
rather than by narrowing the delete: tools live under storageRoot/tools, which
the extension owns, and every fs.rm in toolInstallation.ts is scoped to a
directory it just created or guarded by path.dirname(directory) !== toolsDirectory
plus an lstat().isSymbolicLink() check. I did not have that idea when I wrote
#556, so closing it costs nothing.

#557 — activation raised two information messages on every window open,
V: Update VLS reported "VLS has been restarted after update" after restarting
without fetching anything, v.vls.openOutput was registered but never declared in
contributes.commands, and a showInformationMessage(...).then(...) on the
config listener mutated the shared client outside the awaited path. This PR covers
the same ground as "serialized restarts, crash recovery, status and logs" — the
private pending: Promise.resolve() queue in langserver.ts is a better answer
to the restart race than the flag I added.

Two smaller things from #557 that may be worth folding in here, if they are still
true on this branch:

• v.vls.openOutput needs to appear in contributes.commands or it is
  unreachable from the Command Palette and cannot be bound to a key. If
  v.vls.update sets status.command on failure (langserver.ts), it has to be
  declared too.
• npm run fmt is prettier -w ., and running it reformats the whole repository
  into single quotes, which then fails npm run lint — seven errors in files the
  user never touched. I hit this on fix: stop deleting the user's bin directory when installing V #556 and reverted it. Switching to Oxlint and
  Oxfmt settles it, which is one more reason this branch is the right place to
  land.

Nothing here depends on #554 or #557:

• #558 offers v mcp serve as
  an MCP server, one per workspace folder, read-only by default.
• #559 adds commands for the
  agent skills the compiler ships.

v mcp and v skills are not mentioned anywhere in this PR's description or its
file list, so I read them as separate work. Tell me if they are in scope for 0.3.0
and I will hold them.

The question, then: shall I close #556 and #557 in favour of this one? I am happy
either way — the bugs are real on master today, so if you would rather fix them
before this lands, say so and I will rebase them instead.

One note on the queued runs: both jobs have been queued for about twelve hours
with no runner. If that is a fork-approval thing rather than a busy queue I can
re-run them on request.

[tomaszbk]

Hi @metif12 ! Yes, closing #556 and #557 in favor of this PR makes sense. Both VLS commands are already declared in contributes.commands, and formatting uses Oxfmt with Oxlint.
MCP and compiler skills are outside this PR’s scope, so please continue those separately.

[JalonSolov]

Conflicts to resolve, after recent merges.

[tomaszbk]

Solved @JalonSolov