Skip to main content
Each application is an independent workspace with its own framework dependencies and process smoke test. They import compiled library exports. From the repository root, install the pinned dependencies and build before running a selected example:
The repository uses Bun 1.3.14 as a development package manager. Supported Bun application execution starts at 1.4.4; use the supported runtime when evaluating production behavior. HTTP applications have inspect scripts that connect to an already running example. The stdio Inspector script launches a compiled child process. The root dev command starts every workspace watcher and example server, so use a selected workspace when you only need one application. The protected Clerk flow is explicit: bun run --cwd apps/elysia-example dev:clerk. It requires local keys and OAuth application configuration; ordinary Elysia dev remains credential-free. Its README covers Inspector PKCE configuration. Use framework recipes for the adapter boundaries and the linked source for complete startup/shutdown behavior. Example code is teaching material, not a deployment or credential-management service.