Using CLI
Use the sevok CLI to run a server entry in development or production.
Running the CLI
After installation:
sevok
Without installation:
npx sevok
yarn dlx sevok
pnpm dlx sevok
bunx sevok
deno run -A npm:sevok
Default Entry Resolution
When --entry is omitted, the CLI searches for common entry files such as:
server.tsserver.mjssrc/server.tssrc/server.mjs
If you want to run another filename or a .tsx entry, pass it explicitly.
Usage
sevok <file>
sevok <dir>
sevok --entry <file>
sevok --dir <dir>
Options:
--entry <file> Server entry file to use
--dir <dir> Working directory for resolving entry files
-h, --help Show this help message
-v, --version Show package and runtime versions
-p, --port <port> Port to listen on
--host, --hostname <host> Host to bind to
-s, --static <dir> Serve static files from a directory
--prod Disable watch mode and use production env defaults
--import <module> Preload a module in Node.js or Bun
--tls Enable TLS
--cert <file> TLS certificate file
--key <file> TLS private key file
Examples
Run a standard TypeScript entry
sevok --entry ./server.ts
Run from a working directory
sevok --dir ./apps/api
Use a positional entry
sevok ./server.ts
Serve static files only
sevok --static ./public
Start in production mode
sevok --prod --entry ./server.ts
Run a JSX / TSX entry with jiti
JITI_JSX=1 sevok --entry ./server.tsx --import jiti/register
--import is currently intended for Node.js and Bun. Deno does not use that
flag in this CLI flow.
Environment Variables
PORT: default port when--portis omittedHOST: default host when--host/--hostnameis omittedNODE_ENV: defaults todevelopmentorproductionbased on--prod