Repository navigation
Conversation
karma-typescript is unmaintained since 2023 and runs out of memory with TypeScript >= 5.3, which blocks upgrading TypeScript. Bundle tests with esbuild instead and polyfill Node built-ins (Buffer, assert, zlib) with esbuild-plugin-polyfill-node.
keichi
force-pushed
the
replace-karma-typescript
branch
from
October 15, 2026 13:47
2e6ad84 to
7f2844c
Compare
Owner
Author
|
Closing: karma itself is deprecated and esbuild-plugin-polyfill-node is archived. Migrating to Vitest instead (Node tests first, then browser tests). |
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
karma-typescript(last release 2023) withkarma-esbuildfornpm run test:browser.Buffer,assert,zlib) withesbuild-plugin-polyfill-node.Why
karma-typescriptruns out of memory (heap OOM) with TypeScript >= 5.3, so TypeScript can't be upgraded past 5.2 while it's in use. TypeScript itself is unchanged in this PR; the upgrade will come in a separate PR.Testing
npm run test:browser(ChromeHeadless): 166 SUCCESSnpm teston Node 20: 166 passingNote
esbuildrequires Node >= 18, but thetest-nodejsmatrix (Node 16) and the publish workflow (Node 14) still runnpm ci. Sinceenginesis only a warning,npm cishould still succeed there. I haven't verified this; CI will show it.