Replit

Replit can run DaloyJS as a Node web server. Use the Node adapter, publish as a web server, and make sure the process listens on 0.0.0.0 and the platform-provided PORT. For APIs with variable traffic, start with Autoscale. For always-on workloads or long-running background work, use Reserved VM.

When to choose Replit

• You want browser-based development plus deployment in one place.
• You want Replit Agent to help inspect, modify, and publish the app.
• You are deploying a small to medium Node API and want Autoscale or Reserved VM without writing Docker config.

1. Check Node and pnpm

DaloyJS requires Node.js 24 or newer and pnpm 11 or newer. In Replit Shell, verify the runtime before publishing:

node --version
pnpm --version

Keep the requirement visible in package.json so Replit Agent and the publishing environment do not silently drift to an older runtime:

{
  "engines": {
    "node": ">=24.0.0",
    "pnpm": ">=11.0.0"
  },
  "packageManager": "pnpm@11.0.0"
}

2. Server entrypoint

Bind to all interfaces and use the PORT value provided by Replit. This matters for published apps, not just local preview.

// src/server.ts
import { serve } from "@daloyjs/core/node";
import { app } from "./app.js";

serve(app, {
  port: Number(process.env.PORT ?? 3000),
  hostname: "0.0.0.0",
});

3. Scripts

Keep development and production commands separate. Use the production command in the Publishing pane.

{
  "scripts": {
    "dev": "tsx watch src/server.ts",
    "build": "tsc -p tsconfig.build.json",
    "start": "node dist/server.js"
  }
}

4. Replit app configuration

The .replit file controls the editor Run button. Publishing can also ask for build and run commands in the Publishing pane. Keep them aligned so Preview and the published app behave the same way.

run = "pnpm dev"

[deployment]
build = ["sh", "-c", "pnpm install --frozen-lockfile && pnpm build"]
run = ["sh", "-c", "pnpm start"]

5. Publish

1. Run the app in the Project Editor and open Preview. Fix Preview before publishing.
2. Open Publishing and choose Autoscale for an API that should scale down when idle, or Reserved VM when you need an always-on machine.
3. Set the build command to pnpm install --frozen-lockfile && pnpm build.
4. Set the run command to pnpm start.
5. Choose Web server, not Background worker.
6. Add production Secrets for every required environment variable.

Secrets

Replit Secrets are exposed to the app as environment variables. Add runtime values such as NODE_ENV, database URLs, auth secrets, JWT keys, and webhook secrets through Replit Secrets or published app secrets. Do not commit a .env file.

NODE_ENV=production
SESSION_SECRET=...
DATABASE_URL=...
TRUST_PROXY_HOPS=1

Trust Replit's proxy

Published Replit web apps sit behind Replit's edge proxy. If your DaloyJS app enables production forwarded-header protection, declare the proxy posture instead of disabling the guard:

TRUST_PROXY_HOPS=1

If you put Cloudflare or another proxy in front of Replit, count both hops and use TRUST_PROXY_HOPS=2. See the deployment overview for the proxy posture matrix.

Replit Agent guidance

Replit Agent reads replit.md when it exists in the project root. Add a short file that tells Agent this is a DaloyJS API and that it must keep pnpm, Node 24, security defaults, and the production commands intact:

# DaloyJS API on Replit

- Package manager: pnpm only.
- Runtime: Node.js 24 or newer.
- Build: pnpm build.
- Start: pnpm start.
- Server must bind to process.env.PORT and hostname 0.0.0.0.
- Do not remove secureHeaders(), requestId(), rateLimit(), body limits, request timeouts, or proxy posture checks.
- Store secrets in Replit Secrets, never in committed files.

Gotchas

• Do not bind to localhost or 127.0.0.1 in a published web server. Use 0.0.0.0.
• Do not hard-code PORT=80. Let Replit provide PORT unless you have explicitly configured port mappings.
• Published app secrets are part of publishing setup. Check them when Preview works but the published URL fails.
• The app must keep running. A one-shot script belongs in Scheduled Deployments, not a web-server deployment.
• Replit performs a health check before marking the published app live. Keep startup fast and serve a cheap /healthz endpoint.

See also

• Replit Autoscale Deployments
• Replit Reserved VM Deployments
• Replit publishing troubleshooting
• Replit app configuration
• Replit Secrets
• replit.md