Skip to content

v0.107.2 — The frontend deploy builds again

Shipped 2026-09-23 — a hotfix on main, one commit. v0.107.1's CI deployed the backend but not the frontend: deploy-frontends died in Build VTT frontend with JavaScript heap out of memory.

  • Why now. v0.107.0 added Sentry (frontend monitoring). Once the SENTRY_AUTH_TOKEN / SENTRY_ORG / SENTRY_PROJECT settings exist, the frontend build also generates source maps for upload, and a bundle this size with maps needs more than Node's default ~2 GB heap. The test job's build has no Sentry settings, so it never made maps and passed — which is why only the deploy failed.
  • The fix. The Build VTT frontend step of the production, alpha and dev deploys runs with NODE_OPTIONS=--max-old-space-size=6144. Reproduced locally first: at a 2 GB heap the build fails the same way; at 6 GB it finishes, peaking at 3.2 GB resident. The maps are still uploaded and deleted from dist/ before the S3 sync.