[kkdev92]

Releases 0.10.1: the Windows clipboard read of #119. A patch, because what is saved, where it is saved and what is inserted are unchanged; a paste on Windows only waits less.

What's in it

• version 0.10.1 (npm version, so the lock's root follows).
• CHANGELOG: the [Unreleased] entry becomes [0.10.1] - 2026-11-10, with a summary at the top and the compare links.

Since v0.10.0, what reaches the VSIX is #119. The rest is development dependencies and CI; sharp, @kkdev92/vscode-ext-kit and esbuild are locked at the versions 0.10.0 shipped.

Verification

Verified

• npm run verify on this branch: lint, compile, typecheck:test, test:coverage (581 tests; statements 94.26%, branches 86.66%) and test:e2e (13 passing, exit code 0, VS Code 1.145.2).
• The win32-arm64 VSIX built from this branch has the same dist/extension.js, byte for byte, as the one checked for perf: start Windows PowerShell once, directly, to read the clipboard #119. It differs from that VSIX only in the version and the changelog.
• That VSIX in an isolated VS Code 1.145.2 on Windows 11 ARM64, with a real clipboard: the steps of perf: start Windows PowerShell once, directly, to read the clipboard #119 (a Markdown editor, the terminal, text only) with a bitmap on the clipboard, and again with the clipboard a screenshot tool leaves, an image in the PNG format with a bitmap beside it. The PNG format was given another size than the bitmap, and the saved file had the size of the PNG format, so the paste took the image as it was on the clipboard. 0.10.0 from the Marketplace gives the same results with that clipboard.

Not checked

• What perf: start Windows PowerShell once, directly, to read the clipboard #119 lists as not checked, except the PNG clipboard above: the fallback to PowerShell 7 inside VS Code, and win32-x64 by hand.
• PowerShell still occasionally takes a second or two longer to start. In the checks above, the clipboard read of the first paste in one window took 1.6 s.

🤖 Generated with Claude Code