CI flake: TypeScript - Tests

[clockwork-labs-bot]

Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.

Tests:

• TypeScript - Tests

Error:
Error: command ["pnpm", "-r", "--filter", "./**", "run", "build"] exited with code 133
2026-09-14T14:38:12.7216802Z

Failed job runs:

• https://github.com/clockworklabs/SpacetimeDB/actions/runs/34855333781/job/104018412421 (TypeScript - Tests, attempt 2 -> 3)

Timeout detection:

• none

Context:

• none

[clockwork-labs-bot]

Exact-attempt diagnosis: run 34855333781, job 104018412421, attempt 2, TypeScript - Tests, head afb341d8008c170b8e29ce0f44aea6d2590b38d9 on branch ts-string-codec-fastpath / PR #5783. Setup, checkout, pnpm setup, Rust setup, artifact download, and artifact extraction all succeeded. The failure was in Run TypeScript tests, inside cargo run --timings --package ci-typescript-test --, while it was running pnpm -r --filter ./** run build.

Failure signature: templates/chat-react-ts build crashed the Node/V8 process during tsc -b && vite build:

templates/chat-react-ts build: # Fatal error in , line 0
templates/chat-react-ts build: # RepresentationChangerError: node #425:Phi of kMachNone (NonInternal) cannot be changed to kRepWord32
templates/chat-react-ts build:  2: 0x2a229bb V8_Fatal(char const*, ...) [node]
templates/chat-react-ts build: Failed
ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL @clockworklabs/quickstart-chat@0.0.1 build: `tsc -b && vite build`
Exit status 133

Root cause: this is a Node/V8 internal compiler abort during the template build workload, not a TypeScript assertion/test failure and not a repo formatting/build error. The wrapper then surfaced it as pnpm exit code 133 and ci-typescript-test exit code 1.

Suggested title: CI flake: chat-react-ts build crashes in Node/V8 RepresentationChangerError

Duplicate search: searched the public tracker for the bare Node/V8 fatal family (V8_Fatal, unreachable code, Exit status 133) plus this failure shape (RepresentationChangerError, chat-react-ts build). #5628 is a closed same-family repeat and already points at #5366. #5366 is the closest public canonical tracker for Node/V8 internal aborts during TypeScript/TS build workloads.

Top duplicate candidate: #5366. Leaving this ticket open because #5366 is not one of the configured auto-close targets.