CLI

The elur-kit binary is available after installing the package.

# Commands

# elur-kit build

Builds the static site and client bundle.

elur-kit build

Options:

# elur-kit dev

Starts the dev server with rebuild-on-change. Any source change restarts the worker process.

elur-kit dev

The dev server:

• Watches src/app/, src/islands/, and src/content/ for changes
• Restarts the worker on source changes (no stale module cache)
• Detects atomic saves (sed/editors) via rename events
• Exits cleanly on SIGTERM

# elur-kit preview

Serves the static build in production mode. Falls back to on-demand SSR for routes not in dist/.

elur-kit build
elur-kit preview

# elur-kit start

Runs the SSR server (renders pages on demand, serves static assets from dist/).

elur-kit build
elur-kit start

ISR options:

elur-kit start --cache-dir .elur/cache --default-revalidate 60

# elur-kit adapter <name>

Generates deployment configuration for a target platform.

elur-kit adapter vercel   # → .vercel/output
elur-kit adapter netlify  # → netlify/functions + netlify.toml
elur-kit adapter bun      # → .elur/bun-server.ts
elur-kit adapter node     # → .elur/node-server.mjs

The adapter command also runs validateCapabilities() at build time, so incompatible host/feature combinations (e.g. ISR on a serverless host with no persistent filesystem) fail fast with a diagnostic message instead of producing a broken deployment. See Adapter Capabilities.

# elur-kit check

Runs typecheck + route/config integrity checks. Exits non-zero on errors.

elur-kit check

Combines tsc --noEmit with route manifest validation (duplicate paths, missing dynamic segment params, invalid file conventions).

# elur-kit routes

Lists all discovered routes from src/app/:

elur-kit routes

Output:

GET  /                  src/app/page.ts
GET  /blog/:slug        src/app/blog/[slug]/page.ts
GET  /api/posts         src/app/api/posts/route.ts
*    /__elur/actions  server actions endpoint

# elur-kit doctor

Diagnoses common project issues — missing peer deps, invalid config, stale build artifacts, version mismatches between elur and elur-kit.

elur-kit doctor

# Programmatic API

You can use the CLI programmatically:

import { run, type CliOptions } from "@elurjs/kit";

await run({
  command: "build",
  root: process.cwd(),
  appDir: "src/app",
  islandsDir: "src/islands",
  outDir: "dist",
});

# Bun runtime

For Bun-managed projects, the CLI automatically re-executes itself under the Bun runtime. This ensures bun:sqlite and other Bun-specific APIs work correctly with elur-kit build/dev/start/preview.

# Config file (v2.4.0+)

The kit looks for a config file at the project root:

• elur.config.ts (preferred)
• elur.config.js
• elur.config.mjs
• elur.config.ts (legacy, emits deprecation warning)
• elur.config.js (legacy)
• elur.config.mjs (legacy)

// elur.config.ts
import { defineConfig } from "@elurjs/kit";

export default defineConfig({
  interpolation: "auto", // "auto" | "legacy" | "off"
  images: {
    strict: false, // fail build on image errors
  },
});