chore(deps): bump vscode-languageserver-protocol from 3.17.5 to 3.18.0 in /cddl-lsp/server#575
Closed
dependabot[bot] wants to merge 2 commits into
Conversation
Bumps [vscode-languageserver-protocol](https://github.com/Microsoft/vscode-languageserver-node/tree/HEAD/protocol) from 3.17.5 to 3.18.0. - [Release notes](https://github.com/Microsoft/vscode-languageserver-node/releases) - [Commits](https://github.com/Microsoft/vscode-languageserver-node/commits/release/types/3.18.0/protocol) --- updated-dependencies: - dependency-name: vscode-languageserver-protocol dependency-version: 3.18.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Contributor
Author
|
A newer version of vscode-languageserver-protocol exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
anweiss
added a commit
that referenced
this pull request
Jun 29, 2026
…3.18 Supersedes the individual Dependabot bumps #609, #608 and #575, which failed CI because vscode-languageclient/server v10 expose their `/node` entrypoints via the package `exports` field, which the classic `moduleResolution: "node"` setting cannot resolve (TS2307 on `vscode-languageclient/node`, cascading into missing Node globals). - Bump vscode-languageclient 9 -> 10 (client) and vscode-languageserver 9 -> 10 plus vscode-languageserver-protocol 3.17 -> 3.18 (server). - Switch both LSP tsconfigs to `module`/`moduleResolution: "node16"` so the `exports`-based entrypoints resolve. Because neither package.json declares `"type": "module"`, node16 keeps CommonJS emit (required: the e2e harness runs `client/out/test/*.js` directly under Node, and the extension loads `server/out/server.js`) and uses CommonJS resolution, so the server's `import * as wasm from "../pkg/"` directory specifier still resolves. - Pin the auto-included `@types` via an explicit `types` array so Node globals continue to resolve under the new resolver. Verified locally: `tsc -b` for client and server emit CommonJS, and the full `npm run webpack` production build succeeds. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
anweiss
added a commit
that referenced
this pull request
Jun 29, 2026
…3.18 (#614) Supersedes the individual Dependabot bumps #609, #608 and #575, which failed CI because vscode-languageclient/server v10 expose their `/node` entrypoints via the package `exports` field, which the classic `moduleResolution: "node"` setting cannot resolve (TS2307 on `vscode-languageclient/node`, cascading into missing Node globals). - Bump vscode-languageclient 9 -> 10 (client) and vscode-languageserver 9 -> 10 plus vscode-languageserver-protocol 3.17 -> 3.18 (server). - Switch both LSP tsconfigs to `module`/`moduleResolution: "node16"` so the `exports`-based entrypoints resolve. Because neither package.json declares `"type": "module"`, node16 keeps CommonJS emit (required: the e2e harness runs `client/out/test/*.js` directly under Node, and the extension loads `server/out/server.js`) and uses CommonJS resolution, so the server's `import * as wasm from "../pkg/"` directory specifier still resolves. - Pin the auto-included `@types` via an explicit `types` array so Node globals continue to resolve under the new resolver. Verified locally: `tsc -b` for client and server emit CommonJS, and the full `npm run webpack` production build succeeds. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
auto-merge was automatically disabled
June 29, 2026 21:31
Pull request was closed
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/cddl-lsp/server/vscode-languageserver-protocol-3.18.0
branch
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.
Bumps vscode-languageserver-protocol from 3.17.5 to 3.18.0.
Release notes
Sourced from vscode-languageserver-protocol's releases.
... (truncated)
Commits
2cc5bf0Prepare 3.18 releaseb21577cMerge next release into main (#1778)f168f85Update documentation and fix lint errors (#1770)c54b2fdMerge pull request #1767 from microsoft/dbaeumer/straight-gazelle-plum8f18c48Fix glob pattern documentation (#1769)2d46996Make document color requests consistent with the specification (#1768)2cf625fAdd optional MarkupContent support to diagnostics (#1766)0aa488dInline value clarifications85a9202Migrate to ESLint 9 (#1747)0fae72aUpdate metamodel (#1733)Maintainer changes
This version was pushed to npm by microsoft1es, a new releaser for vscode-languageserver-protocol since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)