chore(deps): update Node package versions across the workspace#72
Merged
Conversation
Bump vite, vitest, typescript, vue, eslint, prettier, @types/node, and
related tooling to their latest compatible versions across all
pnpm-workspace packages (platform/packages/*, extensions/*/packages/*)
and the example apps. Also bumps the pinned pnpm version.
Closes 3 known advisories (vite server.fs.deny bypass - high, vite
launch-editor NTLMv2 disclosure - moderate, js-yaml quadratic DoS via
eslint - moderate); pnpm audit now reports 0 vulnerabilities.
TypeScript is pinned to ^6.0.3 rather than the newly released 7.x:
TS7 restructured its package "exports" map, which breaks vue-tsc's
internal `require('typescript/lib/tsc')` call. vue-tsc stays on the
latest 2.x line (^2.2.12) rather than 3.x, since vue-tsc 3's
@vue/language-core pulls vite-plugin-dts into an experimental Vue-SFC
declaration mode that currently emits broken .d.ts output for this
project's component re-exports.
Also fixes tsconfig gaps surfaced by the @types/node major bump
(TS now requires an explicit "types": ["node"] instead of
auto-including all @types/* packages) and a couple of vitest 4.1 mock
typing regressions in test helpers.
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
vite,vitest,vite-plugin-dts,@vitest/coverage-v8,eslint,prettier,@types/node, and the pinnedpnpmversion to their latest releases across all pnpm-workspace packages (platform/packages/*,extensions/*/packages/*) and the example apps.pnpm auditreported before this change:viteserver.fs.denybypass on Windows alternate paths (GHSA-fx2h-pf6j-xcff)vite/launch-editorNTLMv2 hash disclosure via UNC path handling (GHSA-v6wh-96g9-6wx3)js-yamlquadratic-complexity DoS via repeated aliases, pulled in transitively byeslint(GHSA-h67p-54hq-rp68)pnpm auditnow reports 0 vulnerabilities.typescriptis pinned to^6.0.3rather than the newly released7.x: TS7 restructured its packageexportsmap, which breaksvue-tsc's internalrequire('typescript/lib/tsc')call.vue-tscstays on the latest2.xline (^2.2.12) rather than3.x:vue-tsc3's@vue/language-corepullsvite-plugin-dtsinto an experimental Vue-SFC declaration mode that emits broken.d.tsoutput for this project's component re-exports (confirmed via a clean bisect against the original lockfile).vueitself (the runtime dependency) is updated to its latest release,3.5.39.@types/nodemajor bump: TypeScript no longer auto-includes all@types/*packages without an explicit"types": ["node"], so this is added to thecli,files-sdk, andvuetsconfigs (bothtsconfig.jsonandtsconfig.build.jsonwhere applicable).vitest4.1 mock-typing regressions in test helpers (sdk,saas-sdk,reports-sdk,files-sdk) and onenoUncheckedIndexedAccessstrictness fix in aui-coretest.Verified
pnpm install— clean resolve, noworkspace:*regressions.pnpm -r run typecheck— all 7 typed packages pass.pnpm -r run build— all 7 packages build successfully.pnpm -r run test— 84/84 tests passing across all packages.pnpm audit— 0 vulnerabilities (was 1 high + 2 moderate).Known pre-existing issues (not touched by this PR, out of scope)
pnpm -r run lintwas already broken before this change: noeslint.config.jsexists anywhere in the repo, so ESLint 9+ (already the version pinned before this PR) fails immediately with "couldn't find an eslint.config.js file." Left untouched since fixing it requires designing a lint ruleset, a separate task from a dependency bump.platform/packages/vue'sbuildscript prints benignTS2307: Cannot find module './components/*.vue'diagnostics during.d.tsgeneration. Confirmed via bisect against the original lockfile that this is pre-existing (present before this PR too) and does not fail the build or affect the emitted output.Test plan
pnpm installpnpm -r run typecheckpnpm -r run buildpnpm -r run testpnpm auditGenerated by Claude Code