From addccf469f5d08af762b0f3d3b73a039d29a6328 Mon Sep 17 00:00:00 2001 From: kkdev92 Date: Sat, 29 Aug 2026 02:13:26 +0900 Subject: [PATCH] chore(deps): vscode-ext-kit 4.0.0 The framework raised its own engines.vscode to ^1.134.0, which this extension already declares. `^3.0.0` does not pick up a major, so the two had drifted: the extension required more than the library it is built on. The bundle was built against both versions and compared: exactly one byte of 348,529 differs, and it is meant to. `KIT_VERSION` in src/core/build.ts is inlined at bundle time so the state report can name the kit a build was actually compiled against rather than the semver range -- it now correctly reports 4.0.0. Nothing else moves. Verified: lint, typecheck, check:l10n, 236 unit + 35 integration tests, vsce package, verify:vsix, and the real Extension Host lane (13 cases, VS Code 1.135.0). Co-Authored-By: Claude Opus 5 (1M context) --- CHANGELOG.md | 19 +++++++++++++++++++ package-lock.json | 10 +++++----- package.json | 2 +- 3 files changed, 25 insertions(+), 6 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index eb024b2..85c6576 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,25 @@ All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). +## [Unreleased] + +### Changed + +- `@kkdev92/vscode-ext-kit` `^3.0.0` → `^4.0.0`. The framework raised its own + `engines.vscode` to `^1.134.0`, which this extension already declares, so the + two now agree instead of the extension quietly requiring more than the library + it is built on. + + **One byte of the bundle changes, and it is meant to.** Built both ways and + compared: the esbuild output differs in exactly one byte out of 348,529 — + `KIT_VERSION` in `src/core/build.ts`, which the build inlines so the state + report can name the kit a bundle was actually compiled against rather than + the semver range. It now correctly reports `4.0.0`. Nothing else moves: the + published 3.0.0 and 4.0.0 packages differ only in + `testing/fakes/fake-filewatcher`, which reaches callers through the + `./testing` subpath and never enters a bundle, and all 105 `.d.ts` are + identical. + ## [0.4.0] - 2026-08-29 ### Changed diff --git a/package-lock.json b/package-lock.json index ef61bd4..dd1bfea 100644 --- a/package-lock.json +++ b/package-lock.json @@ -9,7 +9,7 @@ "version": "0.4.0", "license": "MIT", "dependencies": { - "@kkdev92/vscode-ext-kit": "^3.0.0" + "@kkdev92/vscode-ext-kit": "^4.0.0" }, "devDependencies": { "@eslint/js": "^10.0.0", @@ -936,13 +936,13 @@ } }, "node_modules/@kkdev92/vscode-ext-kit": { - "version": "3.0.0", - "resolved": "https://registry.npmjs.org/@kkdev92/vscode-ext-kit/-/vscode-ext-kit-3.0.0.tgz", - "integrity": "sha512-QH6XlqxOc3Jm8a4k4hsyBF+eH/4WOSG6M+YxW0QMlpfLtFr4M4uCUJca5spJpF33NFC8ZliosOSMyVxVWIxjdg==", + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/@kkdev92/vscode-ext-kit/-/vscode-ext-kit-4.0.0.tgz", + "integrity": "sha512-8hKKvRCciiy06wKneqqw/ojE3MKh/gVVyAsWuxeCZeSceR8rKFB6hEt/11eRUVeh3Lf4o/2xsPIDBxasGsdcog==", "license": "MIT", "engines": { "node": ">=22.12.0", - "vscode": "^1.125.0" + "vscode": "^1.134.0" }, "peerDependencies": { "vitest": ">=4" diff --git a/package.json b/package.json index e0efc8b..47447d6 100644 --- a/package.json +++ b/package.json @@ -565,7 +565,7 @@ "clean": "rimraf dist coverage .vsix-verify-temp quick-utils.vsix" }, "dependencies": { - "@kkdev92/vscode-ext-kit": "^3.0.0" + "@kkdev92/vscode-ext-kit": "^4.0.0" }, "devDependencies": { "@eslint/js": "^10.0.0",