Repository navigation
Run the tronbrowser.dev container's API on Bun - #132
Merged
Merged
Conversation
The dev2 image's final stage moves from node:24-bookworm-slim to debian:bookworm-slim plus the bun binary from oven/bun:1.4.0-slim, and start.sh runs the API and the boot-time migration runner with bun. The repo stays a pnpm workspace on Node 24 (desktop, mobile, extension and release builds depend on it), so pnpm still builds and deploys the API in the build stage; only the container runtime changes. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
ThreatCrush Security Scan52 finding(s) HIGH/CRITICAL: 3 | MEDIUM: 28 | LOW: 21
…and 2 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Fleet Node -> Bun migration, batch 3. This PR changes only the dev2 container's runtime. Desktop, mobile, extension and release builds are untouched, and the repo stays a pnpm workspace on Node 24.
Changes
Dockerfile: the final stage moves fromnode:24-bookworm-slimtodebian:bookworm-slimplus thebunbinary fromoven/bun:1.4.0-slim. The pnpm build stage, the engines stage (ungoogled-chromium + Obscura), Caddy and tor are unchanged.start.sh: the migration runner and the API run withbuninstead ofnode. Caddy is still PID 1, so stop behaviour is the same..dockerignore: excludes.gitandnode_modules.ci.yml: a newapi-bunjob. It runs the API's portable tests (12 files; those using vitest-onlyvi.stub*are skipped) underbun test, then migrates a Postgres service and bootsbun services/api/dist/index.js. vitest stays the gate.Verified locally from the commit (
git archive, built image, throwaway Postgres, dummy env)docker topshowsbun /api/dist/index.js. Migrations apply and skip under Bun./api/healthz,/api/1/push,/mcp/tron,/api/auth/me, the 404 page and the www redirect are byte-identical to live.fetch_page(Obscura) andscreenshot_page(spawned Chromium) both work./api/1/push/connecthello, a VAPID push delivered live over the socket, and ping/pong after 65 s idle./me, settings round-trip. A scrypt hash made on Node verifies under Bun.docker stoptakes 0.4 s, and the logs are clean.No tag: a
v*tag ships the desktop release and the package managers.🤖 Generated with Claude Code