Explore new Kickjs agnostic runtime on the alpha channel

The pluggable-HTTP-runtimes work from this RFC (three engines + uploads + runtime typegen) is now on npm under the alpha dist-tag:

Scaffold a new app on any engine

# Fastify
npx @forinda/kickjs-cli@alpha new my-api --runtime fastify

# h3
npx @forinda/kickjs-cli@alpha new my-api --runtime h3

# Express (default) — nothing to choose
npx @forinda/kickjs-cli@alpha new my-api

kick new --runtime installs the right engine peers and writes runtime into kick.config.ts.

Add to an existing app

pnpm add @forinda/kickjs@alpha

import { bootstrap } from '@forinda/kickjs'
import { fastifyRuntime } from '@forinda/kickjs/fastify' // or @forinda/kickjs/h3

export const app = await bootstrap({ modules, runtime: fastifyRuntime() })

Engine peers: Fastify → fastify @fastify/middie (+ @fastify/multipart for uploads); h3 → h3. Express needs nothing extra.

What's in it

• Three engines behind one HttpRuntime seam — Express (default), Fastify, h3 — no controller / module / context-decorator changes.

• File uploads (@FileUpload → ctx.file / ctx.files) on all three: multer (Express), @fastify/multipart (Fastify), native readMultipartFormData (h3). kick add upload installs the right driver.

• Runtime-typed escape hatches — set runtime in kick.config.ts and the kick/runtime typegen retypes ctx.req / ctx.res / AdapterContext.app to the active engine.

• kick doctor validates engine peers + the upload driver.

Docs

• HTTP Runtimes guide + capability matrix

• Migration guide (Express apps need no changes)

• File uploads · bootstrap() options · KickConfig

These are alpha — feedback welcome here while we soak before the stable major. The one remaining item is the h3 v2 web-standard driver (§8) for edge / serverless.