chore: update dev dependencies#794
Merged
Merged
Conversation
- bump @types/vscode to ~1.100.0, swc, eslint, rolldown and related tooling - type the vscode test mock factory against the real `TextDocument` (type-only import) so future `@types/vscode` drift fails once at the factory, not across every call site; adds the newly-required `encoding` property
lcottercertinia
approved these changes
Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 PR Overview
Updates dev tooling dependencies, most notably
@types/vscodeto~1.100.0. The new VS Code types add a requiredencodingproperty toTextDocument, which broke our Jestvscodemock; this also hardens that mock so future type drift is caught in one place rather than across every call site.🛠️ Changes made
@types/vscode~1.99.1→~1.100.0, plus@swc/core,eslint,rolldown,typescript-eslint,lint-stagedand related tooling.createMockTextDocumentfactory against the realvscode.TextDocumentvia a type-only import (erased at runtime, so it doesn't clash with the Jestvscodemodule mapping), replacing the hand-writtenMockTextDocumentinterface that silently drifted.encodingproperty to the mock; cast the four methods returning our simplifiedPosition/Range/TextLinemocks so the object literal stays assigned toTextDocument(missing-property drift now fails once, at the factory).🧩 Type of change (check all applicable)
🔗 Related Issues
✅ Tests added?
📚 Docs updated?
Test plan
pnpm lintpnpm test(folding + language detector suites pass: 23/23)