Skip to content

Migrate dev tooling: TypeScript 7, ESLint 10, Vitest 4, esbuild 0.28 (Dependabot #6) #8

Description

@hhkaos

Dependabot #6 batches six major dev-tooling bumps. Its CI fails and the jumps are breaking, so it was held out of the routine merges. This issue tracks doing it deliberately.

Version jumps (from #6)

Tool From To Risk
typescript ^5.5.0 ^7.0.2 High — 7.x is the native (Go) port, still preview; API/behavior not settled.
eslint + @eslint/js ^9.0.0 ^10.x Medium — flat-config already in use, but rule/preset changes likely.
vitest ^3.0.0 ^4.x Medium — config/API changes across a major.
esbuild ^0.24.0 ^0.28.x Low–Medium — used by apps/editor bundling.
@types/node ^22.0.0 ^26.x Low — but should track the Node runtime (repo targets Node 22).

Why not merged

Suggested approach

Split by tool instead of one batch, each its own PR with green CI:

  1. @types/node — keep aligned with the Node runtime (22 → stay on ^22, or bump runtime first).
  2. esbuild 0.28 — verify apps/editor still bundles (pnpm --filter @opentechevents/editor build).
  3. eslint/@eslint/js 10 — update eslint.config.js for any preset/rule changes.
  4. vitest 4 — run the full suite, fix config/API deltas.
  5. typescript 7 — last, and only if we choose to adopt the preview; otherwise stay on ^5.5 until 7.x is stable. This is the real decision point.

Close #6 in favor of the split PRs, or convert it once rebased per-tool.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions