Skip to content

Vite migration - #448

Merged
derduher merged 1 commit into
masterfrom
vite-migration
Jul 13, 2026
Merged

Vite migration#448
derduher merged 1 commit into
masterfrom
vite-migration

Conversation

@derduher

Copy link
Copy Markdown
Owner

No description provided.

master moved forward while this PR was open with a parallel effort
(f2daca4, 0c2dce1, 7e19ed1) that took webpack in the opposite
direction: npm audit fix --force to webpack 4->5, Jest 26->30,
ESLint 6->10 in place, rather than replacing webpack/Jest with
Vite/Vitest. Both efforts independently hit and fixed the same
underlying issues (Jasmine spyOn syntax, the game.spec.ts timing
flakiness, the same dead-code lint findings, the eslint flat-config
move) since they're inherent to the TS/ESLint major-version jump, not
particular to either build tool.

Superseding the webpack-specific parts: this commit rebuilds the
vite-migration branch on top of master's new tip, keeping the
Vite/vite-plugin-pwa/Vitest approach (which removes webpack/Jest
outright, resolving the same npm audit findings by elimination rather
than upgrade) and dropping master's webpack5/Jest30-specific changes.
Shared tooling versions (eslint, eslint-config-prettier,
eslint-plugin-prettier, typescript-eslint, prettier, globals,
@eslint/js) already matched exactly between the two efforts.

Re-verified end to end after the rebase: tsc --noEmit, eslint, all 49
vitest tests, vite build, and a dev-server smoke check.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@derduher
derduher merged commit fe6b0a2 into master Jul 13, 2026
1 check passed
@derduher
derduher deleted the vite-migration branch July 13, 2026 05:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant