@celsian/vura-core

Core runtime and build pipeline for Vura — the MIT full-stack meta-framework for apps that outgrow serverless.

What it does

@celsian/vura-core scans src/pages and src/api into a route manifest, drives the build pipeline, and provides the runtime helpers your route handlers import: revalidateTag / revalidatePath (backed by what-isr), signed cookie sessions and JWT auth, typed error helpers, and defineConfig. Pages render through What Framework; API routes run on CelsianJS. You normally get this package via npm create vura@latest — install it directly only when building custom adapters or tooling.

Install

npm install @celsian/vura-core

Minimal example

src/api/posts.ts — revalidate a tag on write:

import type { CelsianRequest, CelsianReply } from '@celsian/vura-core';
import { revalidateTag } from '@celsian/vura-core';

export const route = { compute: { class: 'function', memory: '1gb' } };

export async function POST(req: CelsianRequest, reply: CelsianReply) {
  const body = req.parsedBody as { title: string };
  // ... persist the post
  await revalidateTag('posts');
  return reply.json({ ok: true });
}

vura.config.ts — typed project config:

import { defineConfig } from '@celsian/vura-core';

export default defineConfig({
  api: { defaultKind: 'serverless' },
  pages: { defaultMode: 'static' },
});

Documentation

Build manifest compatibility (0.8.3)

build() and direct generateServerEntry() validate metadata using @celsian/vura-contract before producing output. Current unversioned manifests remain accepted explicitly; unknown versions, required features, and invalid metadata fail before build-directory writes. The scanner still emits legacy manifests during the reader-first rollout.

The Node capability declaration describes the existing build-and-serve pipeline, not provider provisioning or isolation. Schedules require task routes; a schedule on an ordinary API route is refused rather than silently ignored. Adapters must establish their own capability support.

• Quick start — /ladder/0-create/
• Config reference — /reference/config/
• API routes — /ladder/3-api/
• Server pages and caching — /ladder/2-cache/
• Route kinds — /reference/route-kinds/

License

MIT — and it will stay MIT.