Next.js Plugin

The @taserjs/plugin/next package hooks Taser.js into Next.js 15+ App Router builds. It generates ${serverDir}/.taserjs/routes.gen.ts from taserjs.config.ts and wires Webpack/Turbopack so routes stay in sync during next dev and next build.

Installation

Install @taserjs/plugin and @taserjs/cli as development dependencies:

Put path layout in taserjs.config.ts:

import { defineConfig } from "@taserjs/cli";

export default defineConfig({
  serverDir: "src/server",
  routesDir: "routes",
  outputDir: ".taserjs",
  app: "taser.ts",
});

Basic Configuration

Wrap next.config.ts with createTaser (or withTaser). Plugin options are only cwd and config:

import type { NextConfig } from "next";
import { createTaser } from "@taserjs/plugin/next";

const nextConfig: NextConfig = {
  reactStrictMode: true,
};

const withTaser = createTaser();

export default withTaser(nextConfig);

Optional overrides:

import { createTaser } from "@taserjs/plugin/next";

const withTaser = createTaser({
  config: "./taserjs.config.ts",
});

export default withTaser({
  reactStrictMode: true,
});

Set the HTTP mount with defineTaser().basePath("/api") in src/server/taser.ts, and point the client baseUrl at the same prefix (for example "/api").

Plugin Options

createTaser accepts NextTaserOptions:

serverDir, routesDir, outputDir, app, and extension come from taserjs.config.ts. Runtime URL prefixes use defineTaser().basePath(...), not plugin options.

How It Works

1. Watches ${serverDir}/routes/ during next dev and regenerates on change (with scaffolding for empty files).
2. Writes ${serverDir}/.taserjs/routes.gen.ts: compiled app, ambient route types, and the composite manifest for @taserjs/client.
3. Hooks Webpack (and keeps Turbopack in sync via the watcher) so builds always see a fresh manifest.

Next Steps