Update dependencies and clean warning sources#133
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the extension’s dependency stack (npm + NuGet) to address Dependabot upgrades and reduce restore/install security warnings, while also tightening a couple of runtime behaviors surfaced by newer tooling (semantic token refresh + floating promises).
Changes:
- Updated client npm dependencies (including
esbuild,js-yamlvia overrides) and refreshedpackage-lock.jsonaccordingly. - Updated server/test NuGet package references to remove/avoid vulnerability warnings during restore/build.
- Made semantic-token refresh best-effort (avoids unhandled rejection if the VS Code command isn’t supported) and fixed a floating-promise lint issue.
Reviewed changes
Copilot reviewed 6 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| src/ServerTests/ServerTests.csproj | Updates MSTest package version. |
| src/Server/Server.csproj | Bumps Kusto SDK and StreamJsonRpc package versions. |
| src/Client/tsconfig.json | Adjusts TS module output setting used for type-checking/bundler-style resolution. |
| src/Client/package.json | Updates dependencies/devDependencies; adds npm overrides and allowScripts entry for esbuild. |
| src/Client/package-lock.json | Lockfile refresh reflecting dependency updates and overrides. |
| src/Client/features/queryEditor.ts | Adds clearer handling for missing history entry and makes semantic token refresh best-effort. |
| src/Client/features/authentication.ts | Fixes a floating promise by explicitly discarding the finally() result. |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
giltayar
approved these changes
Jul 9, 2026
Comment on lines
+991
to
+993
| const headerBytes = encoder.encode(header).length; | ||
| const startFragOffset = headerBytes + encoder.encode(`<!DOCTYPE html><html><body>${startFragment}`).length - encoder.encode(startFragment).length + encoder.encode(startFragment).length; | ||
| const fullBytes = encoder.encode(full).length; |
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.
Summary
esbuildand transitivejs-yaml.esbuildinstall script.MessagePackvulnerability warnings during restore/build.Supersedes / Includes
esbuild0.28.1)js-yaml4.3.0 via override)Validation
npm ci(no deprecation/audit/allow-scripts warnings)npm audit(0 vulnerabilities)npm run type-checknpm run lintnpm test(499 passed)npm run compilenpm run test:integration(46 passed)dotnet build src/Server/Server.csproj(noMessagePackvulnerability warnings)dotnet run --project src/ServerTests/ServerTests.csproj(200 passed)Notes
The remaining debug-console lines seen during integration are VS Code/test-harness or other-extension noise (
DEP0190, mutex/shared storage, test dialog refusal, file watcher reveal messages). The first-partyvscode.executeDocumentSemanticTokensProviderunhandled rejection from the runtime debug console is removed.