Change Log

June 20, 2026 · View on GitHub

1.1.4

Added localization support via @vscode/l10n. All parser diagnostics, validation messages, and client-side error strings are now translatable.
Added package.nls.json for localizable contributes strings (display name, configuration title and description).
Added l10n/bundle.l10n.json as the English source bundle for all runtime strings.
Added extract-l10n npm script to regenerate bundle.l10n.json from source; runs automatically as part of package:local and vscode:prepublish.
Migrated server from vscode-nls to @vscode/l10n.
Added sbom, sbom:cyclonedx, and sbom:spdx npm scripts to generate CycloneDX and SPDX SBOM outputs.
Improved parsing reliability and error reporting for malformed structures and invalid numeric values, reducing false or confusing diagnostics.
Improved editing experience by making value completions work after both = and : assignment styles.
Added regression tests to keep these parsing and diagnostic improvements stable over time.
Improved test runner reliability in local/CI environments.

Fixed repository URL in package.json (was pointing to mtayler, now correctly points to borkra).
Fixed LibConfigServer.trace.server configuration key casing to match the LSP client ID so VS Code trace logging works correctly.
Release script (scripts/update-version.js) now removes the ## Unreleased section entirely on publish instead of leaving a placeholder.
Bumped @types/node from ^16.0.0 to ^18.0.0 in server and client to match the minimum VS Code Node runtime.

Documented the public parser provider API for extension-to-extension integration (getParsedDocument, API versioning, and consumer example).
Better reliability on modern VS Code versions thanks to a language server stack upgrade (vscode-languageclient/vscode-languageserver 9.x).
Set compatibility to VS Code 1.82.0 and newer.
Internal cleanup: updated to current language server APIs and removed unused or no longer required code.
Better compatibility guidance: missing ;/, terminators and trailing commas in lists/arrays now show portability warnings instead of being silently accepted or always rejected.
Fewer false alarms: spec-variant syntax no longer triggers incorrect error diagnostics.
Safer numeric parsing: invalid signed base-prefixed values (for example +0x10, -0b11) are now consistently rejected.
More stable extension reload/reinstall behavior by fixing activation and disposal lifecycle issues.
Better syntax support for @include "path" directives.
Better boolean compatibility: true/false are now parsed case-insensitively.
Better numeric compatibility: binary (0b/0B) and octal (0o/0O, 0q/0Q) forms are now supported.
Improved numeric handling by allowing hex digits of arbitrary length.
Better editor responsiveness by fixing parser recovery loops that could cause hang and 100% CPU utilizaton.
Added context-aware autocomplete suggestions for booleans, @include directives, value snippets, and setting/group templates.