zapstudio.dev valid

Zap Studio

Type-safe, framework-agnostic and composable TypeScript libraries for the web.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T10:06:42.499Z. Cached copy · Source on zapstudio.dev

# Zap Studio

> Type-safe, framework-agnostic and composable TypeScript libraries for the web.

## When to use Zap Studio

Zap Studio is a set of small, type-safe, framework-agnostic TypeScript packages
for the infrastructure code every app needs: HTTP calls, retries, authorization
checks, validation, logging, webhooks. Reach for a package here instead of
hand-rolling the same logic per project. Install one with
`npm install @zap-studio/<name>`, or `deno add jsr:@zap-studio/<name>`.

Every runtime package ships standard ESM and targets Node.js 18+, Bun 1.0+,
Deno 1.42+, Cloudflare Workers, and evergreen browsers.

- **@zap-studio/cache** — Zero-dependency in-memory key-value cache with pluggable eviction policies (LRU, LFU, MRU, MFU, FIFO), capacity limits, and optional TTL.
- **@zap-studio/env** — A runtime and framework-agnostic, Standard Schema-based environment variable validator.
- **@zap-studio/fetch** — A type-safe, tree-shakeable fetch wrapper for HTTP requests with runtime schema validation.
- **@zap-studio/logger** — A lean, tree-shakeable logging abstraction with a console implementation.
- **@zap-studio/monads** — Result/Option types and Rust-style functional combinators for explicit, type-safe error handling.
- **@zap-studio/oxfmt** — Zap Studio's oxfmt preset: sorted imports, sorted package.json, and an optional Tailwind CSS class-sorting extension.
- **@zap-studio/oxlint** — Zap Studio's oxlint preset: exclusive, single-owner rule sets — pick exactly the presets your project needs, nothing implied.
- **@zap-studio/permit** — A type-safe, declarative, tree-shakeable authorization library for TypeScript with Standard Schema support.
- **@zap-studio/react-hooks** — Small, focused, tree-shakeable React hooks — one hook, one subpath, no forced bundle.
- **@zap-studio/retry** — Composable, tree-shakeable retry policies for resilient async operations.
- **@zap-studio/store** — Small, framework-agnostic state container with auto-tracked derived values and optional built-in persist.
- **@zap-studio/validation** — Tree-shakeable Standard Schema utilities and ValidationError helpers.
- **@zap-studio/webhooks** — A lightweight, type-safe, tree-shakeable webhook router with Standard Schema validation, signature verification, and lifecycle hooks.
- **@zap-studio/webmcp** — A framework-agnostic, SSR-safe wrapper around the native WebMCP document.modelContext API, with a batch tool registry for exposing JavaScript tools to AI agents.

## Docs

- [Getting Started](https://www.zapstudio.dev/docs): Type-safe, framework-agnostic TypeScript packages for HTTP calls, retries, auth, validation, logging, and webhooks — install one and make your first typed call.
- [Installation](https://www.zapstudio.dev/docs/installation): Install any Zap Studio package from npm or JSR, pick the peer dependencies you need, and import only the code you use.
- [Runtimes](https://www.zapstudio.dev/docs/runtimes): The runtimes every Zap Studio package supports, the shared bas
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=zapstudio.dev · GET /v1/domain/zapstudio.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 zapstudio.dev:
1. POST https://agentwebmap.com/v1/sites/zapstudio.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://zapstudio.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/zapstudio.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/zapstudio.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.