Skip to content

chore(web): pin web runtime to Node 24.16.0-alpine - #1498

Merged
2witstudios merged 1 commit into
masterfrom
chore/web-node24-runtime
Jun 2, 2026
Merged

2witstudios merged 1 commit into
masterfrom
chore/web-node24-runtime

Conversation

@2witstudios

@2witstudios 2witstudios commented Jun 2, 2026 •

Copy link
Copy Markdown
Owner

Bumps the web Docker image (deps/builder/runner) from node:22.17.0-alpine → node:24.16.0-alpine.

Why

The agent code-execution driver (@fly/sprites, default-OFF in #1487) is Node 24+/ESM-only and loads in-process in the web server, so enabling code execution requires the web runtime on Node 24. This lands that prerequisite separately from the dark feature.

Validation (local)

Full production image build on node:24.16.0-alpine succeeds end-to-end:

  • bun install --frozen-lockfile ✅
  • @pagespace/db + @pagespace/lib build ✅
  • next build — compiled, 208/208 static pages generated ✅
  • Image runs Node v24.16.0, no EBADENGINE/engine warnings, @fly/sprites present in tree ✅

Scope / risk

  • Web only. processor (TensorFlow native, highest ABI-rebuild risk) intentionally stays on Node 22; realtime/admin/marketing untouched.
  • Web has no native deps + alpine base + Next.js 15 → low risk; the build proved it out.
  • Independent of Agent Code Execution — bash/code in chat via Fly Sprites (epic) #1487 (which ships dark); merge order doesn't matter, but the feature can't be enabled until this is deployed.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated the Node.js runtime to version 24.16.0 for improved performance and stability.

Bumps the apps/web Docker image (deps/builder/runner stages) from
node:22.17.0-alpine to node:24.16.0-alpine.

Why: the agent code-execution driver (`@fly/sprites`, behind the default-OFF
flag in PR #1487) is Node 24+/ESM-only. The web process loads it in-process, so
enabling code execution requires the web runtime on Node 24. This is the
prerequisite runtime bump, landed separately from the (dark) feature.

Validated: full production image build on node:24.16.0-alpine succeeds —
bun install, @pagespace/db + @pagespace/lib build, and `next build`
(208/208 static pages) all pass; image runs Node v24.16.0; no engine warnings.
Scoped to web only — processor (TensorFlow native) stays on Node 22.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 2, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
pagespace-marketing Ready Ready Preview, Comment Jun 2, 2026 4:33pm

@coderabbitai

coderabbitai Bot commented Jun 2, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b629959c-70ce-4af0-8c3d-5d61782ade73

📥 Commits

Reviewing files that changed from the base of the PR and between 897ca62 and ebdaf36.

📒 Files selected for processing (1)
  • apps/web/Dockerfile

📝 Walkthrough

Walkthrough

apps/web/Dockerfile updates all three build stages (deps, builder, runner) from node:22.17.0-alpine to node:24.16.0-alpine. The multi-stage Docker build flow remains unchanged: Bun installs monorepo dependencies, the source is copied, packages are built, and the final runner image is produced with production assets and NODE_ENV=production.

Changes

Node.js base image upgrade

Layer / File(s) Summary
Node.js 24 base image across all stages
apps/web/Dockerfile
All three build stages (deps, builder, runner) update from node:22.17.0-alpine to node:24.16.0-alpine, updating the runtime environment for dependency installation, builds, and the production container.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

  • #1491: Bumping the web app's base image from Node 22 to Node 24 directly addresses the runtime mismatch that prevents @fly/sprites from loading in the web process.

Poem

🐰 A Docker base update, so clean and precise,
From twenty-two to twenty-four, the Node.js slice,
Three stages leap forward with each alpine run,
Runtime and builds aligned—the Node upgrade's done! 🚀

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: bumping the Node.js runtime version for the web application from 22.17.0-alpine to 24.16.0-alpine in the Dockerfile.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/web-node24-runtime

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@2witstudios
2witstudios merged commit 1446c00 into master Jun 2, 2026
5 checks passed
@2witstudios
2witstudios deleted the chore/web-node24-runtime branch June 5, 2026 18:49

This branch was previously deployed

1 inactive deployment
Preview — ebdaf362 Deployed Jun 2, 2026 by vercel[bot]
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