test: stabilize tester app compilation tests

[dannyhw]

Summary

• run tester-app test files sequentially to avoid concurrent webpack and Rspack compilation competing for runner CPU
• retain the existing 60-second compilation-test timeouts
• replace the touched unsafe TypeScript suppression with an expected-error directive

Why

The main test matrix and release workflows both timed out in the webpack iOS bundle test at exactly 60 seconds after the lazy-compilation integration test was added. The production bundle path is unaffected by lazy compilation. Instead, Vitest ran the new lazy-compilation file concurrently with the existing bundle and start test files, causing several full webpack and Rspack compilations to compete for runner CPU.

Serializing the tester-app files removes that contention without relaxing the timeout that detects unexpectedly slow compilation.

Failed runs:

• https://github.com/callstack/repack/actions/runs/32485399065
• https://github.com/callstack/repack/actions/runs/32485398765

Validation

• PR CI Checks passed
• full Test Main Matrix passed with the original 60-second limits:
  • Node 18
  • Node 20
  • Node 22
  • Node 24
  • Node 26
• matrix run: https://github.com/callstack/repack/actions/runs/32595949422

[changeset-bot]

⚠️ No Changeset found

Latest commit: 69cdec3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
repack-website	Ready	Preview	Aug 22, 2026 8:11pm