Fix type-related build failures in sqlite package#208
Conversation
Co-authored-by: rzhao271 <7199958+rzhao271@users.noreply.github.com>
|
@copilot Downgrade all workflows to Node 22 to align with VS Code, and resolve any new typing issues that show up. |
Co-authored-by: rzhao271 <7199958+rzhao271@users.noreply.github.com>
Done in 371ce36. Updated all pipeline/workflow files to Node 22 ( |
|
@copilot minor versions aren't consistent. Use 22.22.0 on all workflows. Engine requirement should just be 22 |
Co-authored-by: rzhao271 <7199958+rzhao271@users.noreply.github.com>
Done in 3d592a4. All workflow files now use |
vscode-languageserver-protocolwas imported in thesqlitepackage but never declared as a dependency.Changes
sqlite/package.jsonvscode-languageserver-types: ^3.17.5as an explicit dependency@types/nodeto22.19.15>=22sqlite/src/compress.ts,sqlite/src/blobStore.tsimport * as lsp from 'vscode-languageserver-protocol'withvscode-languageserver-types— all consumed types (Range,Diagnostic,FoldingRange,DocumentSymbol,Hover,MarkupContent,MarkedString) are available in the lighter types-only package, which is already a transitive dependency vialsif-protocolpackage.json@types/nodeto22.19.15protocol/package.json,language-service/package.json>=22build/azure-pipelines/linux/build.yml,build/azure-pipelines/win32/build.yml,build/azure-pipelines/lsif-repository-tests.yml22.22.0to align with VS Codebuild/azure-pipelines/pipeline.yml22.22.0💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.