taserjs.dev valid

Taser.js API Router Quick Reference

Taser.js is a type-safe, file-based REST API router for TypeScript. Packages: `@taserjs/router`, `@taserjs/cli`, `@taserjs/plugin`, `@taserjs/client`. Runs on Vite standalone, Nitro, Next.js App Router, TanStack Start, and host pass-through (Express, Fastify, Hono).

For agents: Taser.js docs: type-safe, file-based REST API router for TypeScript with automatic client generation, running on Vite, Nitro, Next.js and more.

typescriptrest api routerfile-based routingvitenextjs

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T22:11:31.180Z. Cached copy · Source on taserjs.dev

# Taser.js API Router Quick Reference

> Taser.js is a type-safe, file-based REST API router for TypeScript. Packages: `@taserjs/router`, `@taserjs/cli`, `@taserjs/plugin`, `@taserjs/client`. Runs on Vite standalone, Nitro, Next.js App Router, TanStack Start, and host pass-through (Express, Fastify, Hono).

## Canonical Architecture
- App definition: `export default defineTaser({ ... })` from `@taserjs/router` (uninstantiated `TaserDefinition`).
- Generated entry: `src/.taserjs/routes.gen.ts` exports runnable `app`, ambient types, and `AppManifest`.
- Paths: configure `serverDir` / `routesDir` / `outputDir` in `taserjs.config.ts` via `@taserjs/cli`.
- Mount URL prefix with `defineTaser().basePath("/api")` — never on plugin options.
- Next plugin options are only `cwd?` and `config?` (`createTaser` from `@taserjs/plugin/next`).

## Core File Naming Conventions
- Root Route: `src/routes/index.get.ts` -> GET /
- Dynamic Param: `src/routes/users/$id.get.ts` -> GET /users/:id
- Optional Param: `src/routes/posts/{-$category}.get.ts` -> GET /posts/:category? (matches /posts and /posts/:category; `req.params.category: string | undefined`)
- Nested Flat Route: `src/routes/users.$id.posts.get.ts` -> GET /users/:id/posts
- Catch-All Splat: `src/routes/files.$.get.ts` -> GET /files/* (`req.params._splat`)
- Pathless Layout: `src/routes/_auth.ts` -> Scoped middleware for pathless group
- Directory Layout: `src/routes/api/$.ts` -> Scoped middleware for /api/*

## Route Handler Pattern
```ts
import { json, notFound } from "@taserjs/router/reply";
import { t } from "@taserjs/router";
import { z } from "zod";

const GET = t
  .get("/users/:id")
  .params(z.object({ id: z.string().uuid() }))
  .query(z.object({ limit: z.coerce.number().default(10) }))
  .returns({
    200: z.object({ id: z.string(), name: z.string() }),
    404: z.object({ message: z.string() }),
  });

export default GET.handler(async ({ req, ctx }) => {
  const user = await ctx.db.findUser(req.params.id);
  if (!user) {
    return notFound({ message: "User not found" });
  }
  return json(user);
});
```

## Middleware & Layout Pattern
Handler/middleware args are facet-split: `{ req, ctx, state, ...services }`.
```ts
import { unauthorized } from "@taserjs/router/reply";
import { t } from "@taserjs/router";

export default t.layout("/dashboard").use(async ({ req }, next) => {
  const authHeader = req.headers.get("authorization");
  if (!authHeader) {
    return unauthorized({ message: "Missing authorization" });
  }
  return next({ user: { id: "user_123", role: "admin" } });
});
```

## Cookies
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=taserjs.dev · GET /v1/domain/taserjs.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for taserjs.dev:
1. POST https://agentwebmap.com/v1/sites/taserjs.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://taserjs.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/taserjs.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/taserjs.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.