Conversation
There was a problem hiding this comment.
Pull request overview
Updates monorepo dev-tooling dependencies (testing/build/lint-related) across workspaces, refreshing the Yarn lockfile accordingly.
Changes:
- Bump Vitest (and related
@vitest/*) to^4.1.0across packages. - Bump
tsdownto^0.21.4across packages. - Refresh additional dev dependencies (Commitlint, Storybook, Testing Library, JSDOM, Turbo, types packages) and regenerate
yarn.lock.
Reviewed changes
Copilot reviewed 12 out of 13 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| yarn.lock | Regenerated lockfile reflecting updated dev dependency graph (Vitest/Storybook/JSDOM/Turbo/etc.). |
| package.json | Updates root devDependencies (commitlint, vitest, turbo, coverage). |
| packages/sel-types/package.json | Bumps tsdown and vitest. |
| packages/sel-schema/package.json | Bumps @types/node, tsdown, and vitest. |
| packages/sel-runtime/package.json | Bumps @types/debug, tsdown, and vitest. |
| packages/sel-env/package.json | Bumps tsdown and vitest. |
| packages/sel-editor/package.json | Bumps jsdom, tsdown, and vitest. |
| packages/sel-editor-react/package.json | Bumps Storybook/Testing Library/JSDOM/React types, plus tsdown and vitest. |
| packages/sel-common/package.json | Bumps tsdown and vitest. |
| packages/sel-checker/package.json | Bumps @types/debug, tsdown, and vitest. |
| packages/sel-cel-lezer/package.json | Bumps tsdown and vitest. |
| packages/fixtures/package.json | Bumps tsdown and vitest. |
| packages/e2e/package.json | Bumps vitest. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "sort-package-json": "^3.6.1", | ||
| "turbo": "^2.8.17", | ||
| "vitest": "^4.0.18" | ||
| "turbo": "^2.8.20", |
There was a problem hiding this comment.
With the Vitest bump to ^4.1.0, the dependency tree now brings in Vite 8.x (per yarn.lock), but this root package.json doesn’t declare a Vite version. To avoid peer-dependency warnings and keep tooling on a consistent Vite major, consider adding an explicit vite devDependency here (or a workspace-level resolutions entry) matching the version you intend to support.
| "turbo": "^2.8.20", | |
| "turbo": "^2.8.20", | |
| "vite": "^8.0.0", |
f5fc838 to
a7e90c5
Compare
No description provided.