Repository navigation
chore: update npm dependencies - #115
Merged
Merged
Conversation
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.
A manual pass that follows
renovate.json: all npm dependencies in one group, pinned to exact versions, non-major updates only. The GitHub Actions in use are already on their latest majors (checkoutv7,setup-nodev7,action-gh-releasev3), so nothing changes there.Updates
@modelcontextprotocol/sdkwseslintpublint@types/node@types/wsThe other dev dependencies are pinned at their current versions.
npm audit fix(without--force) then moved transitive versions in the lockfile, sonpm auditgoes from 20 findings onmainto 0.SDK note
SDK 1.32.1 fixes GHSA-6qxp-vccf-f47h. That advisory is in the OAuth client, which this stdio server doesn't import, but 1.25.2 was flagged for it.
SDK 1.29+ maps its
./*wildcard types to*.js.d.tsfiles it doesn't ship. That breaks ESLint'simport-x/no-unresolvedfor@modelcontextprotocol/sdk/server/mcp.jsand similar imports. Node,tscand esbuild still resolve them.eslint.config.mjstherefore ignores only^@modelcontextprotocol/sdk/for that rule. I checked that a missing local import is still reported.Verification
tsc --noEmitreports the same 2 errors asmain. Both predate this change, andtscisn't part of CI.tools/listoutput is byte-identical tomain: 125 tools, 168,274 characters.Majors held for separate review
@modelcontextprotocol/inspector0.22 → 2.10: dev-only debugger, but a major API and CLI change.typescript5.9 → 7.0: the native compiler port.zod3 → 4: bundled, so it changes how tool schemas are generated.esbuild0.25 → 0.28: minor bumps on 0.x can break, and it produces the published bundle.@types/node22 → 26:enginesis>=22.18, so this stays on 22.renovate.jsonnow limits@types/nodeto22.x, so Renovate won't propose newer majors.Smoke test
chore/deps, then runnpm installandnpm run watch. Connect the Editor on port 52000. It shows connected.list_entitiesand thencapture_viewport. They return the scene's entities and a screenshot, as onmain.