ReDock + Node.js
Node, per site.
Each site declares its Node version; ReDock installs the verified build once and reconfigures serving in seconds when you switch. Your system stays exactly as it was.
Free · works with Node.js as Node.js · official marks, interoperability only What ReDock does with it
Every version, per site.
22 · 20 · 18, side by side Self-contained builds with pinned checksums, each living entirely under ReDock's directory.
Pin from a dropdown Site → Setup → Node. Switch, and the site is re-served on the new version without a restart ritual.
Builds and dev servers Headless front ends, Shopify apps, plain Node services: ReDock runs them supervised, logs streaming, health watched.
Build it in an afternoon
Upgrade a project to Node 22 safely
Three steps, one window, receipts for the parts the agent did.
- 01Create a universe of the site on a new branch.
- 02Set its Node to 22; run the build; read the logs.
- 03Green? Merge from the Git tab. Red? Delete the universe; the original never moved.
Node.js on the blog
Shopify The Shopify dev environment checklist: Node versions, env files, Postgres A pre-flight checklist for a working Shopify app dev environment, the right Node version, seeded env files, a session Postgres, and a public HTTPS tunnel. Read → Shopify Shopify app development on localhost: tunnels, OAuth, and webhooks that work A local Shopify app dev environment needs a public HTTPS tunnel, the right Node version, seeded env files, and a session store, here's how to get all four. Read →
Calm ships tonight.
Download ReDock, berth your first site, and watch the AI work, receipts and all. Five minutes, no terminal.
Free · macOS and Windows · your sites stay on your machine