Runtime adapters

Jinatra's core speaks Fetch. Adapters connect the same app to a local server without changing route code.

Bun

import { app } from 'jinatra'
import { serve } from 'jinatra/bun'

serve(app, {
  port: 3000,
  static: './public',
})

The Bun adapter uses Bun.serve(), supports static files, and exposes listen as an alias for serve.

Node

import { app } from 'jinatra'
import { serve } from 'jinatra/node'

serve(app, {
  port: 3000,
  static: './public',
})

The Node adapter bridges Node's HTTP server to Web Request and Response objects. It requires Node 18 or newer.

Any Fetch runtime

The core app can be exported directly:

import { Jinatra } from 'jinatra'

const app = new Jinatra()
app.get('/', () => 'Hello')

export default { fetch: app.fetch }

app.fetch(request, env, executionContext) is the portable integration point for runtimes that already provide a Fetch server.

Multiple ports and subdomains

Separate apps can listen on different ports:

const web = new Jinatra()
const api = new Jinatra()

web.get('/', () => 'Website')
api.get('/users', () => [{ id: 1 }])

serve(web, { port: 3000 })
serve(api, { port: 3001 })

For subdomains, dispatch by hostname in a Fetch-compatible entry point:

const web = new Jinatra()
const api = new Jinatra()

web.get('/', () => 'Website')
api.get('/users', () => [{ id: 1 }])

export default {
  fetch(request, env, ctx) {
    const host = new URL(request.url).hostname
    const target = host === 'api.example.com' ? api : web
    return target.fetch(request, env, ctx)
  },
}

A reverse proxy can also map subdomains to separate ports. Jinatra does not require a special subdomain abstraction.

Static files

The Bun and Node adapters can serve a directory after Jinatra returns a 404:

serve(app, {
  static: {
    directory: './public',
    cacheControl: 'public, max-age=3600',
  },
})

Static serving includes MIME types, HEAD, cache headers, traversal protection, and optional SPA fallback configuration.