@nifrajs/cli 2.6.0 → 2.7.0

package/dist/cli.js

@@ -134,7 +134,7 @@ routes/ from the current directory. Run from your project root.
 Port: \`dev\` and \`start\` share the default ${DEFAULT_DEV_PORT}. Override with \`--port <n>\` (alias \`-p\`) or the
 \`PORT\` env var (\`--port\` wins over \`PORT\`, which wins over the default).`;
 // Kept in lockstep with packages/cli/package.json by check:publish's version-consistency gate.
-const CLI_VERSION = "2.6.0";
+const CLI_VERSION = "2.7.0";
 // A render adapter + nifra server are opaque to the CLI (it just forwards them); cast at the seam.
 const asAdapter = (v) => v;
 const asBunPlugins = (v) => v;

package/dist/mcp-http.js

@@ -23,7 +23,7 @@ import { loadTypesCorpus } from "./types-search.js";
 export { examplesAppTool, examplesWidget } from "./mcp-app-tool.js";
 export { docsTools } from "./mcp-docs-tools.js";
 // Kept in lockstep with packages/cli/package.json by check:publish's version-consistency gate.
-const VERSION = "2.6.0";
+const VERSION = "2.7.0";
 const SERVER_INFO = { name: "nifra-docs", version: VERSION };
 // Derive the GET/health tool list from the tools actually served, so the line can never drift from them.
 const docsHealth = (tools) => `nifra docs MCP - POST JSON-RPC 2.0 here (methods: initialize, tools/list, tools/call). Tools: ${tools

package/docs/llms-full.txt

@@ -186,12 +186,13 @@ to full-stack later without a rewrite.
 -
 **Throughput - the realistic case.** Router micro-benchmarks flatter Hono (a single compiled
 regex), but a router is **~1% of a real request** - the time goes to middleware, validation,
-context, and serialization. On the bare Bun/Deno micro-GET rows Nifra runs within **~1-3% of
-Elysia** - a statistical tie at the runtime ceiling; on **Node it's ahead of Elysia on every
-workload**, and it leads on every POST/validated row across runtimes. In the realistic shape
-(security headers + CORS + bearer auth + cookies + validated query/body + a ~2.4 KB JSON
-response, measured with `oha`) Nifra runs at **103% of Elysia on GET and 108% on
-POST**. Treat benchmark rows as same-run evidence, not a permanent law of nature.
+context, and serialization. In the current Bun matrix Nifra **matches or beats Elysia on three
+of the four workloads** (medians 101%, 104%, 99%, 101%) and takes the top `GET /`
+row outright; on **Node it leads the whole framework field - Elysia, Fastify, Hono, Express -
+on every workload**. In the realistic shape (security headers + CORS + bearer auth + cookies +
+validated query/body + a ~2.4 KB JSON response, measured with `oha`) Nifra runs
+at **103% of Elysia on GET and 108% on POST**. Treat benchmark rows as same-run evidence, not
+a permanent law of nature.
 
 -
 **End-to-end types.** `client<typeof app>()` derives request inputs _and_
@@ -3452,6 +3453,16 @@ my-app/
   backend.ts         # export const backend = server()...   (optional - the typed contract)
 ```
 
+These paths are **fixed**, not configurable: the CLI resolves all four from the
+project root, so `backend.ts` cannot move into `src/` or be renamed -
+if the file is not at the root, `nifra dev|build` simply run without a backend
+(it is optional, so nothing errors). Only the entry file is pinned; the feature modules it
+`.merge()`s can live in any directory. Keep `backend.ts` a pure
+composition root - merging modules, registering no routes of its own - so each route's
+capability reach stays its own module's (see
+[Backends & API](/docs/backends) and
+[Verification](/docs/verification)).
+
 ### framework.ts - naming the framework once
 
 Keep the render `adapter` in deploy-safe `framework.ts`. Put
@@ -8415,10 +8426,14 @@ bun create nifra my-app
 
 - **`api`** - a typed nifra server (`src/app.ts` + `src/index.ts`) with an example test and
   `dev`/`start`/`test`/`typecheck` scripts.
-- **`site`** - a nifra + React SSR site, one source deployable to Cloudflare Pages, Node, Deno, or
-  Vercel Edge.
+- **`site`** - the full-stack template: a nifra + React SSR site (file-routed frontend + typed
+  `backend.ts`), one source deployable to Cloudflare Pages, Node, Deno, or Vercel Edge. Pick the
+  frontend with `--framework react|preact|vue|solid|svelte`.
 - **`isr`** - a nifra + React app with **Incremental Static Regeneration** on Cloudflare Workers + KV
   (pages cached + served stale-while-revalidate; on-demand purge endpoint).
+- **`batteries`** - the `api` starter plus the batteries a real API needs: background jobs
+  (`@nifrajs/jobs`), a TTL cache (`@nifrajs/cache`), blob storage (`@nifrajs/storage`), and cursor
+  pagination (`@nifrajs/schema`).
 
 ```sh
 bun create nifra my-app --template isr

package/docs/types.json

@@ -10814,14 +10814,14 @@
     "name": "VERSION",
     "kind": "const",
     "package": "@nifrajs/core",
-    "signature": "export declare const VERSION: \"2.6.0\";",
+    "signature": "export declare const VERSION: \"2.7.0\";",
     "doc": "/**\n * Current package version. A hardcoded literal on purpose - core runs on the edge (no fs), so it can't\n * read its own package.json at runtime. `scripts/version.ts` rewrites it on every release bump and\n * `check:publish` asserts it equals `@nifrajs/core`'s package version.\n */"
   },
   {
     "name": "VERSION",
     "kind": "const",
     "package": "nifra",
-    "signature": "export declare const VERSION: \"2.6.0\";",
+    "signature": "export declare const VERSION: \"2.7.0\";",
     "doc": "/**\n * Current package version. A hardcoded literal on purpose - core runs on the edge (no fs), so it can't\n * read its own package.json at runtime. `scripts/version.ts` rewrites it on every release bump and\n * `check:publish` asserts it equals `@nifrajs/core`'s package version.\n */"
   },
   {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nifrajs/cli",
-  "version": "2.6.0",
+  "version": "2.7.0",
   "description": "The nifra CLI - zero-config dev/build/start for a nifra app (`nifra dev`, `nifra build`, `nifra start`).",
   "keywords": [
     "bun",
@@ -41,14 +41,14 @@
     "access": "public"
   },
   "dependencies": {
-    "@nifrajs/client": "2.6.0",
-    "@nifrajs/core": "2.6.0",
-    "@nifrajs/mcp": "2.6.0",
-    "@nifrajs/runner": "2.6.0",
-    "@nifrajs/schema": "2.6.0",
-    "@nifrajs/testing": "2.6.0",
-    "@nifrajs/web": "2.6.0",
-    "create-nifra": "2.6.0"
+    "@nifrajs/client": "2.7.0",
+    "@nifrajs/core": "2.7.0",
+    "@nifrajs/mcp": "2.7.0",
+    "@nifrajs/runner": "2.7.0",
+    "@nifrajs/schema": "2.7.0",
+    "@nifrajs/testing": "2.7.0",
+    "@nifrajs/web": "2.7.0",
+    "create-nifra": "2.7.0"
   },
   "repository": {
     "type": "git",

package/src/cli.ts

@@ -154,7 +154,7 @@ Port: \`dev\` and \`start\` share the default ${DEFAULT_DEV_PORT}. Override with
 \`PORT\` env var (\`--port\` wins over \`PORT\`, which wins over the default).`
 
 // Kept in lockstep with packages/cli/package.json by check:publish's version-consistency gate.
-const CLI_VERSION = "2.6.0"
+const CLI_VERSION = "2.7.0"
 
 // A render adapter + nifra server are opaque to the CLI (it just forwards them); cast at the seam.
 const asAdapter = (v: unknown): RenderAdapter => v as RenderAdapter

package/src/mcp-http.ts

@@ -29,7 +29,7 @@ export { docsTools } from "./mcp-docs-tools.ts"
 export type { TypeEntry } from "./types-search.ts"
 
 // Kept in lockstep with packages/cli/package.json by check:publish's version-consistency gate.
-const VERSION = "2.6.0"
+const VERSION = "2.7.0"
 const SERVER_INFO = { name: "nifra-docs", version: VERSION }
 // Derive the GET/health tool list from the tools actually served, so the line can never drift from them.
 const docsHealth = (tools: McpTool[]): string =>