# Pitlane

> Portable platform integration for Remix 3.

Pitlane gives you composable packages to help you put your Remix app on the grid. Its packages are independent: @pitlane/vite-plugin-remix (build & develop), @pitlane/content (load & validate), @pitlane/theme (style & compose), @pitlane/crawler (crawl & prerender), @pitlane/data-table-d1 (connect your data).

Start with [Pitlane guides](https://pitlane.tools/guides.md). [The home page](https://pitlane.tools/index.md) shows what each package is for, with an example.

Every page listed here is Markdown, at its HTML page's address with `.md` added, or `index.md` for an address ending in `/`. [llms-full.txt](https://pitlane.tools/llms-full.txt) holds every page in one file.

## Getting Started

- [Pitlane guides](https://pitlane.tools/guides.md): An introduction to Pitlane, a composable toolkit for Remix 3, with guides for each task.
- [Installing Pitlane](https://pitlane.tools/guides/umbrella.md): Install every Pitlane package with one dependency, import each through a pitlane/* subpath, and decide when the scoped @pitlane/* packages fit better.

## Vite Plugins

- [Using the Vite plugin](https://pitlane.tools/guides/vite-plugin.md): How the remix() plugin from pitlane/vite-plugin-remix behaves in your app day to day, across document assets, the clientEntry() transform and its footguns, dev-server semantics, preview, and the build.
- [Hot module replacement](https://pitlane.tools/guides/hmr.md): How the pitlane/vite-plugin-remix Vite plugin hot-updates a Remix 3 app during vite dev, covering which component edits swap in place, which remount, how server-only edits revalidate through the frame runtime, and the requirements and limits of both halves.
- [Single-page apps](https://pitlane.tools/guides/spa.md): How remix({ server: false }) sets up a client-rendered Remix 3 app, and what the plugin still contributes once there is no server.
- [Fetch server](https://pitlane.tools/guides/fetch-server.md): Serve a Vite app's development requests through the Fetch handler your server module exports, with fetchServer() from pitlane/vite-plugin-fetch-server, alone or beside assets().

## Assets

- [Asset resolution](https://pitlane.tools/guides/assets.md): Resolve browser entries, stylesheets, preload hints, and import maps from a Vite build or dev server with pitlane/assets, in a Remix app or any other server-rendered app.
- [Manifest integrations](https://pitlane.tools/guides/asset-build.md): Produce an asset manifest from any bundler's output with createAssetManifest from pitlane/assets/build, and consume it through createAssetResolver without Vite.

## Deployment

- [Deploy to Cloudflare Workers](https://pitlane.tools/deploy/cloudflare.md): Run a Remix 3 app on Cloudflare Workers with pitlane/vite-plugin-remix and the Cloudflare Vite plugin, with workerd in dev, Miniflare preview, and wrangler deploy.
- [Deploy to Netlify](https://pitlane.tools/deploy/netlify.md): Run a Remix 3 app on Netlify with pitlane/vite-plugin-remix: a one-file Netlify Function wraps the built fetch handler, and the Netlify Vite plugin emulates the platform locally.
- [Deploy to Vercel](https://pitlane.tools/deploy/vercel.md): Run a Remix 3 app on Vercel with pitlane/vite-plugin-remix and the Nitro Vite plugin, which produces Vercel Functions through the Build Output API.
- [Deploy to Railway](https://pitlane.tools/deploy/railway.md): Run a Remix 3 app on Railway under Node, Bun, or Deno: the built fetch handler plus one Dockerfile.
- [Deploy to Railway (No Build)](https://pitlane.tools/deploy/railway-no-build.md): Run a Remix 3 app on Railway under Node, Bun, or Deno straight from source: one Dockerfile that installs dependencies and starts server.ts, with no build step.
- [Deploy to Deno Deploy](https://pitlane.tools/deploy/deno-deploy.md): Run a Remix 3 app on Deno Deploy: the built fetch handler behind a three-line Deno.serve entrypoint, built and deployed by Deploy's own infrastructure.
- [Deploy to Deno Deploy (No Build)](https://pitlane.tools/deploy/deno-deploy-no-build.md): Run a Remix 3 app on Deno Deploy straight from source. Deploy installs dependencies, and Deno runs the TypeScript behind a three-line Deno.serve entrypoint with no build step.
- [Deploy to GitHub Pages](https://pitlane.tools/deploy/github-pages.md): Deploy a Remix 3 app to GitHub Pages, in SPA mode with remix({ server: false }) or as a fully prerendered build, covering the base path and the 404.html fallback a project site needs.

## Crawler

- [Crawler](https://pitlane.tools/guides/crawler.md): How pitlane/crawler walks a Remix 3 fetch router in memory, and the jobs that walk is good for: sitemaps, link checks, and render smoke tests.
- [Prerendering](https://pitlane.tools/guides/prerendering.md): How remix({ prerender }) renders paths to static HTML during vite build, and where the paths come from.
- [Prerendering (No Build)](https://pitlane.tools/guides/prerendering-no-build.md): How @pitlane/crawler renders an app's paths to static HTML from a script with no bundler, and where the paths come from.

## Theme

- [Theme](https://pitlane.tools/guides/theme.md): Style Remix apps with remix/component css mixins and pitlane/theme design tokens.

## Content

- [Content](https://pitlane.tools/guides/content.md): How pitlane/content turns Markdown, MDX, and data files into schema-validated collections a Remix 3 controller can query, prebuilt into the bundle by the contentLayer() Vite plugin.
- [Content (No Build)](https://pitlane.tools/guides/content-no-build.md): How pitlane/content turns Markdown, MDX, and data files into schema-validated collections a Remix 3 controller can query, served straight from source with Sätteri rendering at request time.

## Data

- [Cloudflare D1](https://pitlane.tools/guides/cloudflare-d1.md): How pitlane/data-table-d1 runs Remix 3's data-table on Cloudflare D1, and which parts of D1 the driver cannot paper over.

## @pitlane/assets API

- [@pitlane/assets](https://pitlane.tools/package/assets/index.md): Framework-neutral asset resolution: construct a resolver from the manifest a build integration supplies, and read browser-entry URLs, preloads, stylesheets, and import maps from it.
- [createAssetResolver](https://pitlane.tools/package/assets/function/createAssetResolver.md): Constructs the resolver for a manifest, usually the default export of `@pitlane/assets/manifest`. Construct it once, in a module of the app's own.
- [renderImportMap](https://pitlane.tools/package/assets/function/renderImportMap.md): Serializes an import map into an inline `<script type="importmap">` element for server-rendered HTML, or `""` when the map has no mappings.
- [AssetEnvironment](https://pitlane.tools/package/assets/interface/AssetEnvironment.md): Every source module observed in one environment's graph, keyed by portable source key.
- [AssetMetadata](https://pitlane.tools/package/assets/interface/AssetMetadata.md): The JavaScript and CSS one source module requires in one environment.
- [AssetResolver](https://pitlane.tools/package/assets/interface/AssetResolver.md): Resolves portable source keys, such as `app/entry.browser.ts` or `file:app/counter.tsx#Counter`, to the URLs a build or development server produced for them.
- [BuildAssetsManifest](https://pitlane.tools/package/assets/interface/BuildAssetsManifest.md): The manifest a production build produces.
- [DevAssetsManifest](https://pitlane.tools/package/assets/interface/DevAssetsManifest.md): The manifest a development server supplies, refreshed as the graph changes.
- [ImportMap](https://pitlane.tools/package/assets/interface/ImportMap.md): An import map as the HTML standard defines it: specifier mappings, optional scoped mappings, and optional integrity metadata.
- [RenderImportMapOptions](https://pitlane.tools/package/assets/interface/RenderImportMapOptions.md): Options for [renderImportMap](https://pitlane.tools/package/assets/function/renderImportMap.md).
- [ScriptEntry](https://pitlane.tools/package/assets/interface/ScriptEntry.md): What a browser needs to load one script entry: its URL, the URLs worth `modulepreload` hints, and the import map its imports resolve through.
- [AssetsManifest](https://pitlane.tools/package/assets/type/AssetsManifest.md): Everything `createAssetResolver` accepts. `{ mode: "unavailable" }` is what `@pitlane/assets/manifest` exports when no build integration replaced it.

## @pitlane/assets/build API

- [@pitlane/assets/build](https://pitlane.tools/package/assets/build.md): Bundler-neutral manifest generation for integration authors: describe what a bundler emitted as an [AssetBuild](https://pitlane.tools/package/assets/build/interface/AssetBuild.md), and [createAssetManifest](https://pitlane.tools/package/assets/build/function/createAssetManifest.md) returns the manifest `createAssetResolver` reads.
- [createAssetManifest](https://pitlane.tools/package/assets/build/function/createAssetManifest.md): Converts a bundler's normalized output into the manifest `createAssetResolver` reads.
- [AssetBuild](https://pitlane.tools/package/assets/build/interface/AssetBuild.md): A bundler's output, normalized for `createAssetManifest`.
- [AssetBuildChunk](https://pitlane.tools/package/assets/build/interface/AssetBuildChunk.md): One emitted JavaScript chunk.
- [AssetBuildEnvironment](https://pitlane.tools/package/assets/build/interface/AssetBuildEnvironment.md): One environment's output graph.

## @pitlane/assets/manifest API

- [@pitlane/assets/manifest](https://pitlane.tools/package/assets/manifest.md): 
- [default](https://pitlane.tools/package/assets/manifest/variable/default.md): `{ mode: "unavailable" }`, until `assets()` or an alias replaces this module.

## @pitlane/assets/vite-plugin API

- [@pitlane/assets/vite-plugin](https://pitlane.tools/package/assets/vite-plugin.md): 
- [assets](https://pitlane.tools/package/assets/vite-plugin/function/assets.md): The Vite plugins that give `@pitlane/assets` its manifest: they serve browser entries during `vite dev`, emit them in a build, and replace `@pitlane/assets/manifest` with the manifest of the current dev server or build. Setting `allowFiles` also enforces the browser boundary.
- [AssetEntryRegistration](https://pitlane.tools/package/assets/vite-plugin/interface/AssetEntryRegistration.md): Browser entries declared by one server module's development transform.
- [AssetsPluginApi](https://pitlane.tools/package/assets/vite-plugin/interface/AssetsPluginApi.md): Available on the resolved plugin named `pitlane-assets`.
- [AssetsPluginOptions](https://pitlane.tools/package/assets/vite-plugin/interface/AssetsPluginOptions.md): Options for [assets](https://pitlane.tools/package/assets/vite-plugin/function/assets.md). `remix()` from `@pitlane/vite-plugin-remix` accepts them as `remix({ assets })`.
- [ASSETS_MANIFEST_FILE](https://pitlane.tools/package/assets/vite-plugin/variable/ASSETS_MANIFEST_FILE.md): The manifest module a build writes at the root of each server environment's output directory. The server chunks that read the manifest import this file by a relative path, so a host that deploys a single module must bundle it in.

## @pitlane/content API

- [@pitlane/content](https://pitlane.tools/package/content/index.md): Schema-validated, cross-referenced content collections for Remix 3.
- [createContent](https://pitlane.tools/package/content/function/createContent.md): Declares a set of content collections.
- [Collection](https://pitlane.tools/package/content/interface/Collection.md): The query surface of one collection.
- [CollectionDefinition](https://pitlane.tools/package/content/interface/CollectionDefinition.md): What `c.collection({ loader, schema })` returns.
- [ContentBuilder](https://pitlane.tools/package/content/interface/ContentBuilder.md): The builder `createContent` hands to its callback.
- [ContentLoader](https://pitlane.tools/package/content/interface/ContentLoader.md): A loader that resolves a whole collection by filling a store.
- [Entry](https://pitlane.tools/package/content/interface/Entry.md): One entry of a collection, as a caller sees it.
- [EntryBody](https://pitlane.tools/package/content/interface/EntryBody.md): The raw source of an entry's document, before anything renders it.
- [GenerateIdOptions](https://pitlane.tools/package/content/interface/GenerateIdOptions.md): Options handed to a `loaders.glob` `generateId` function.
- [Heading](https://pitlane.tools/package/content/interface/Heading.md): A heading collected from a Markdown or MDX document.
- [LiveEntry](https://pitlane.tools/package/content/interface/LiveEntry.md): What a [LiveLoader](https://pitlane.tools/package/content/interface/LiveLoader.md) returns for one entry.
- [LiveLoader](https://pitlane.tools/package/content/interface/LiveLoader.md): A loader that answers one query at a time.
- [LoadedEntry](https://pitlane.tools/package/content/interface/LoadedEntry.md): What a [ContentLoader](https://pitlane.tools/package/content/interface/ContentLoader.md) writes into the store for one entry.
- [LoaderContext](https://pitlane.tools/package/content/interface/LoaderContext.md): What a loader is handed to read its source and validate what it found.
- [Reference](https://pitlane.tools/package/content/interface/Reference.md): A resolved pointer from one entry to another, produced by `c.reference(collection)`.
- [RenderedEntry](https://pitlane.tools/package/content/interface/RenderedEntry.md): What `entry.render()` resolves to.
- [CollectionEntry](https://pitlane.tools/package/content/type/CollectionEntry.md): One entry of `collection`, named the way an application thinks of it: `CollectionEntry<typeof content.blog>`.
- [Content](https://pitlane.tools/package/content/type/Content.md): The object `createContent` returns: one [Collection](https://pitlane.tools/package/content/interface/Collection.md) per key of the definitions its callback returned, named after that key and typed by the output of that collection's schema.
- [Loader](https://pitlane.tools/package/content/type/Loader.md): Either kind of loader.
- [ReferenceSchema](https://pitlane.tools/package/content/type/ReferenceSchema.md): The schema `c.reference(collection)` returns: a Standard Schema that reads an entry id (a string) and outputs a [Reference](https://pitlane.tools/package/content/interface/Reference.md) into `collection`.

## @pitlane/content/hot API

- [@pitlane/content/hot](https://pitlane.tools/package/content/hot.md): Browser reloads during development when a file behind a collection changes, for servers that `remix/node-hmr` supervises rather than Vite. See [hotContent](https://pitlane.tools/package/content/hot/function/hotContent.md).
- [hotContent](https://pitlane.tools/package/content/hot/function/hotContent.md): Reloads the browser when a file behind a collection changes.
- [BrowserEvent](https://pitlane.tools/package/content/hot/interface/BrowserEvent.md): An event for the browser HMR client. A reload is the only one content sends.
- [BrowserHmrChannel](https://pitlane.tools/package/content/hot/interface/BrowserHmrChannel.md): The part of `remix/node-hmr`'s `BrowserHmrChannel` this module uses.
- [FileEvent](https://pitlane.tools/package/content/hot/interface/FileEvent.md): A file change the supervisor's watcher observed.

## @pitlane/content/loaders API

- [@pitlane/content/loaders](https://pitlane.tools/package/content/loaders.md): The two built-in loaders for collections on the filesystem: [glob](https://pitlane.tools/package/content/loaders/function/glob.md) reads every file a pattern matches as one entry, and [file](https://pitlane.tools/package/content/loaders/function/file.md) reads one JSON or YAML file holding many entries.
- [file](https://pitlane.tools/package/content/loaders/function/file.md): Reads one file holding many entries.
- [glob](https://pitlane.tools/package/content/loaders/function/glob.md): Reads every file a pattern matches as one entry.

## @pitlane/content/satteri API

- [@pitlane/content/satteri](https://pitlane.tools/package/content/satteri.md): Sätteri plugins that Markdown and MDX entry bodies need: [headings](https://pitlane.tools/package/content/satteri/function/headings.md) collects the heading list `render()` returns, and [rawStyles](https://pitlane.tools/package/content/satteri/function/rawStyles.md) keeps the CSS inside a `<style>` element intact. With a Vite build, register both with `vite-plugin-satteri`; without one, `render()` applies them itself.
- [headings](https://pitlane.tools/package/content/satteri/function/headings.md): Collects every heading of a document as `{ depth, slug, text }`, publishes the list as `data.headings`, and gives each heading an `id` matching its slug so an anchor link lands on it. A heading's text is the text it shows on the page, as `visibleText` reads it. On MDX the list is also appended to the tree as `export const headings`, so the compiled module carries its own table of contents.
- [rawStyles](https://pitlane.tools/package/content/satteri/function/rawStyles.md): Hands a `<style>` element's CSS to Remix as markup rather than as text, so the stylesheet survives being rendered.

## @pitlane/content/vite-plugin API

- [@pitlane/content/vite-plugin](https://pitlane.tools/package/content/vite-plugin.md): The [contentLayer](https://pitlane.tools/package/content/vite-plugin/function/contentLayer.md) Vite plugin, which resolves every collection during the build and inlines the entries into the bundle, so a host with no filesystem serves the same collections.
- [contentLayer](https://pitlane.tools/package/content/vite-plugin/function/contentLayer.md): Resolves content collections during the build and inlines them.

## @pitlane/crawler API

- [@pitlane/crawler](https://pitlane.tools/package/crawler/index.md): `crawl()` — spider a Remix 3 fetch router in memory. Requests go straight into `router.fetch`, so an app can be walked and written to disk without a socket, a server, or a browser. `staticPaths()` answers the question that comes first: which paths a route map can serve with no params.
- [crawl](https://pitlane.tools/package/crawler/function/crawl.md): Walks an app by dispatching requests straight into its router, yielding each response as it arrives. No socket, no server, no browser: the router's `fetch` is the whole transport, so this runs anywhere the app itself runs.
- [staticPaths](https://pitlane.tools/package/crawler/function/staticPaths.md): Collects every path in a route map that can be requested without params: the Remix 3 answer to "what pages does this app have", and the input a prerender pass needs before it knows any dynamic values.
- [CrawlOptions](https://pitlane.tools/package/crawler/interface/CrawlOptions.md): What [crawl](https://pitlane.tools/package/crawler/function/crawl.md) fetches and how: the starting paths, whether to follow links and queue assets, how many requests run at once, and hooks for `nofollow` pages and redirects. Every option has a default, so `crawl(router)` walks everything reachable from `/`.
- [CrawlResult](https://pitlane.tools/package/crawler/interface/CrawlResult.md): One fetched path and the response the router produced for it.
- [CrawlTarget](https://pitlane.tools/package/crawler/interface/CrawlTarget.md): What [crawl](https://pitlane.tools/package/crawler/function/crawl.md) needs from a router. A `createRouter()` router satisfies it, and so does anything else that answers a `Request` — a built server bundle's default export, a worker-style `{ fetch }` object, a test double.

## @pitlane/data-table-d1 API

- [@pitlane/data-table-d1](https://pitlane.tools/package/data-table-d1/index.md): A Cloudflare D1 driver for Remix 3's `data-table`.
- [createD1Database](https://pitlane.tools/package/data-table-d1/function/createD1Database.md): Wraps a D1 binding in a `Database`.
- [D1Database](https://pitlane.tools/package/data-table-d1/class/D1Database.md): A `Database` bound to Cloudflare D1.
- [D1DatabaseDriver](https://pitlane.tools/package/data-table-d1/class/D1DatabaseDriver.md): A `DatabaseDriver` backed by a Cloudflare D1 binding.
- [D1BatchResult](https://pitlane.tools/package/data-table-d1/interface/D1BatchResult.md): What one statement in a [D1DatabaseDriver.batch](https://pitlane.tools/package/data-table-d1/class/D1DatabaseDriver.md#batch) produced.
- [D1Binding](https://pitlane.tools/package/data-table-d1/interface/D1Binding.md): The slice of Cloudflare's D1 API this driver uses.
- [D1DatabaseOptions](https://pitlane.tools/package/data-table-d1/interface/D1DatabaseOptions.md): The options [createD1Database](https://pitlane.tools/package/data-table-d1/function/createD1Database.md) accepts: `remix/data-table`'s `DatabaseOptions`, plus D1's statement observer and transaction mode.
- [D1DriverOptions](https://pitlane.tools/package/data-table-d1/interface/D1DriverOptions.md): The options [D1DatabaseDriver](https://pitlane.tools/package/data-table-d1/class/D1DatabaseDriver.md) accepts: the D1-specific half of [D1DatabaseOptions](https://pitlane.tools/package/data-table-d1/interface/D1DatabaseOptions.md), which [createD1Database](https://pitlane.tools/package/data-table-d1/function/createD1Database.md) passes through.
- [D1Meta](https://pitlane.tools/package/data-table-d1/interface/D1Meta.md): What D1 reports about one statement it ran.
- [D1PreparedStatement](https://pitlane.tools/package/data-table-d1/interface/D1PreparedStatement.md): A statement [D1Binding.prepare](https://pitlane.tools/package/data-table-d1/interface/D1Binding.md#prepare) returns, before it runs.
- [D1Result](https://pitlane.tools/package/data-table-d1/interface/D1Result.md): What one statement produced: its rows, empty for a write, and D1's metadata.
- [D1StatementReport](https://pitlane.tools/package/data-table-d1/interface/D1StatementReport.md): What one executed statement cost, as D1 reported it.
- [D1StatementObserver](https://pitlane.tools/package/data-table-d1/type/D1StatementObserver.md): Called after each statement the driver executes.
- [D1TransactionMode](https://pitlane.tools/package/data-table-d1/type/D1TransactionMode.md): How the driver answers a `transaction()` call.

## @pitlane/data-table-d1/migrations API

- [@pitlane/data-table-d1/migrations](https://pitlane.tools/package/data-table-d1/migrations.md): Compiles `data-table` migrations into the flat `.sql` files Wrangler's D1 migration runner reads.
- [generateD1Migrations](https://pitlane.tools/package/data-table-d1/migrations/function/generateD1Migrations.md): Writes one `<id>_<name>.sql` per migration into `options.to`, then deletes generated files with no migration behind them, so the output directory is a pure function of the input one.
- [GenerateD1MigrationsOptions](https://pitlane.tools/package/data-table-d1/migrations/interface/GenerateD1MigrationsOptions.md): What [generateD1Migrations](https://pitlane.tools/package/data-table-d1/migrations/function/generateD1Migrations.md) needs to know.
- [GeneratedD1Migration](https://pitlane.tools/package/data-table-d1/migrations/interface/GeneratedD1Migration.md): One generated file.

## @pitlane/theme API

- [@pitlane/theme](https://pitlane.tools/package/theme/index.md): Type-safe styling with design tokens for Remix 3.
- [combine](https://pitlane.tools/package/theme/function/combine.md): Composes [tva](https://pitlane.tools/package/theme/function/tva.md) components, like cva's `compose`. Each input resolves independently against the shared props, the results deep-merge in argument order, and one [css](https://pitlane.tools/package/theme/function/css.md) call produces the descriptor. The result accepts the union of the inputs' props and honors each input's own defaults.
- [createTheme](https://pitlane.tools/package/theme/function/createTheme.md): Compiles a theme from a schema tree and the token tree it describes.
- [css](https://pitlane.tools/package/theme/function/css.md): Brand-enforced wrapper over `remix/component`'s `css()` mixin. Token-mapped longhands accept the matching token brand, CSS-wide keywords, property keywords, and `0`; anything else — including a raw `color: "#ff0000"` — is a type error. Every other CSS property carries csstype's value union, so `display`, `position`, `resize`, and the rest of the closed-grammar properties accept only their real keywords. Nested selectors, at-rules, and custom properties recurse.
- [cx](https://pitlane.tools/package/theme/function/cx.md): clsx-compatible `className` joiner for interop with plain stylesheets, since `mix` and `className` compose on the same element. Strings and numbers join with spaces, falsy values drop, arrays flatten, and truthy object keys join.
- [lightDark](https://pitlane.tools/package/theme/function/lightDark.md): A `light-dark()` color, resolved by the browser against the `color-scheme` property. A subtree that sets `color-scheme` flips whatever the media query says, which is what a theme toggle needs.
- [scale](https://pitlane.tools/package/theme/function/scale.md): Turns one token into a multiplier, so a scale does not have to name every step. The returned function produces `calc(<base> * <steps>)`, keeping whichever brand the base carried.
- [tva](https://pitlane.tools/package/theme/function/tva.md): Builds a variant resolver modeled on [cva](https://cva.style). Where cva composes class strings, `tva` composes brand-enforced style objects into a `mix`-ready descriptor.
- [ThemeError](https://pitlane.tools/package/theme/class/ThemeError.md): The error [createTheme](https://pitlane.tools/package/theme/function/createTheme.md) throws for every structural failure: one problem, one sentence.
- [CombinedTVAFn](https://pitlane.tools/package/theme/interface/CombinedTVAFn.md): A component built by [combine](https://pitlane.tools/package/theme/function/combine.md). Accepts the union of the input components' props and honors each input's own defaults.
- [ScaleFn](https://pitlane.tools/package/theme/interface/ScaleFn.md): The accessor leaf for a token declared with `s.scale()`: callable for steps, with the base itself as `.token`.
- [ThemeComponent](https://pitlane.tools/package/theme/interface/ThemeComponent.md): The `<Theme />` component [createTheme](https://pitlane.tools/package/theme/function/createTheme.md) returns. Render it once near the document root to install the custom properties.
- [ThemedCSSProps](https://pitlane.tools/package/theme/interface/ThemedCSSProps.md): The style-object type accepted by [css](https://pitlane.tools/package/theme/function/css.md) and every [tva](https://pitlane.tools/package/theme/function/tva.md) slot.
- [ThemeInit](https://pitlane.tools/package/theme/interface/ThemeInit.md): The argument [createTheme](https://pitlane.tools/package/theme/function/createTheme.md) accepts: a schema tree, the token tree it describes, and any modes.
- [ThemeMode](https://pitlane.tools/package/theme/interface/ThemeMode.md): A theme's mode: a condition plus the values it overrides.
- [ThemePatch](https://pitlane.tools/package/theme/interface/ThemePatch.md): The argument `extend` accepts. `schema` is optional, because a patch that only adds tokens to an existing namespace needs no new entry.
- [ThemeResult](https://pitlane.tools/package/theme/interface/ThemeResult.md): The object [createTheme](https://pitlane.tools/package/theme/function/createTheme.md) returns: the typed token accessor, the `raw` resolver, the `<Theme />` component, and the two derivation methods.
- [Tokens](https://pitlane.tools/package/theme/interface/Tokens.md): The token tree [createTheme](https://pitlane.tools/package/theme/function/createTheme.md) accepts: nested records whose leaves are [TokenValue](https://pitlane.tools/package/theme/type/TokenValue.md)s. No reserved keys, so it is plain JSON and a designer can diff it.
- [TVAConfig](https://pitlane.tools/package/theme/interface/TVAConfig.md): Configuration for [tva](https://pitlane.tools/package/theme/function/tva.md). Every style slot is [ThemedCSSProps](https://pitlane.tools/package/theme/interface/ThemedCSSProps.md), carrying the same brand enforcement as [css](https://pitlane.tools/package/theme/function/css.md).
- [TVAFn](https://pitlane.tools/package/theme/interface/TVAFn.md): A variant component built by [tva](https://pitlane.tools/package/theme/function/tva.md). Call it with a variant selection to get a `mix`-ready descriptor; call `resolve` for the merged [ThemedCSSProps](https://pitlane.tools/package/theme/interface/ThemedCSSProps.md) without building a descriptor.
- [AnyToken](https://pitlane.tools/package/theme/type/AnyToken.md): The union of all twelve token brands. Brands are compile-time tags naming each token's type; they let [css](https://pitlane.tools/package/theme/function/css.md) reject a dimension where a color belongs. They exist only in the type system — every ref is a plain string at runtime, so brands cost nothing — and they are theme-independent, so tokens minted by two different [createTheme](https://pitlane.tools/package/theme/function/createTheme.md) calls mix freely in one [css](https://pitlane.tools/package/theme/function/css.md) call.
- [BorderToken](https://pitlane.tools/package/theme/type/BorderToken.md): Compile-time brand for a `border` token.
- [ClassValue](https://pitlane.tools/package/theme/type/ClassValue.md): A value [cx](https://pitlane.tools/package/theme/function/cx.md) accepts: a string, a number, a nested array of the same, or a record whose truthy keys are emitted. `null`, `undefined`, and `false` are dropped. Compatible with clsx.
- [ColorToken](https://pitlane.tools/package/theme/type/ColorToken.md): Compile-time brand for a `color` token.
- [CubicBezierToken](https://pitlane.tools/package/theme/type/CubicBezierToken.md): Compile-time brand for a `cubicBezier` token.
- [DeepPartialTokens](https://pitlane.tools/package/theme/type/DeepPartialTokens.md): The mode-override shape for a token tree: every group optional, every leaf a value. A mode overrides values, never structure or types.
- [DimensionToken](https://pitlane.tools/package/theme/type/DimensionToken.md): Compile-time brand for a `dimension` token.
- [DurationToken](https://pitlane.tools/package/theme/type/DurationToken.md): Compile-time brand for a `duration` token.
- [FontFamilyToken](https://pitlane.tools/package/theme/type/FontFamilyToken.md): Compile-time brand for a `fontFamily` token.
- [FontWeightToken](https://pitlane.tools/package/theme/type/FontWeightToken.md): Compile-time brand for a `fontWeight` token.
- [GradientToken](https://pitlane.tools/package/theme/type/GradientToken.md): Compile-time brand for a `gradient` token.
- [NumberToken](https://pitlane.tools/package/theme/type/NumberToken.md): Compile-time brand for a `number` token.
- [ShadowToken](https://pitlane.tools/package/theme/type/ShadowToken.md): Compile-time brand for a `shadow` token.
- [StrokeStyleToken](https://pitlane.tools/package/theme/type/StrokeStyleToken.md): Compile-time brand for a `strokeStyle` token.
- [ThemedCSSMixin](https://pitlane.tools/package/theme/type/ThemedCSSMixin.md): The descriptor [css](https://pitlane.tools/package/theme/function/css.md) produces. `MixinDescriptor` is invariant in its node type, so — exactly like `remix/component`'s own `css` factory — the node binds per callsite through the generic parameter.
- [ThemeProps](https://pitlane.tools/package/theme/type/ThemeProps.md): Props for the [ThemeComponent](https://pitlane.tools/package/theme/interface/ThemeComponent.md). `nonce` sets the `nonce` attribute on the emitted `<style>` element for Content Security Policy setups.
- [TokenTree](https://pitlane.tools/package/theme/type/TokenTree.md): The accessor shape for an init `T`: the same nesting as its token tree, with every leaf replaced by the branded `var(--…)` reference its schema declares. Numeric keys index with brackets (`t.color.gray[900]`).
- [TokenType](https://pitlane.tools/package/theme/type/TokenType.md): The twelve DTCG token `$type` values.
- [TokenValue](https://pitlane.tools/package/theme/type/TokenValue.md): A token value: the CSS it becomes. A string, a number, or an array of either. Anything else is a group.
- [TransitionToken](https://pitlane.tools/package/theme/type/TransitionToken.md): Compile-time brand for a `transition` token.
- [TVAProps](https://pitlane.tools/package/theme/type/TVAProps.md): Extracts a [tva](https://pitlane.tools/package/theme/function/tva.md) component's variant props, like cva's `VariantProps`. All props are optional; wrap the component to require one.
- [UntypedToken](https://pitlane.tools/package/theme/type/UntypedToken.md): Compile-time brand for a token declared with `s.any()`. It carries no CSS type, so the open-grammar properties (`animation`, `aspectRatio`, `background`) accept it and the token-mapped longhands reject it.

## @pitlane/theme/default API

- [@pitlane/theme/default](https://pitlane.tools/package/theme/default.md): Tailwind CSS v4's default primitive theme as a ready-made [DefaultTheme](https://pitlane.tools/package/theme/default/variable/DefaultTheme.md) component: colors, spacing, radii, fonts, shadows, easing, and the rest of Tailwind's primitives. Select the primitives an application uses, and give them semantic names, in a theme built from it.
- [DefaultTheme](https://pitlane.tools/package/theme/default/variable/DefaultTheme.md): Tailwind CSS v4.3.2's default primitive theme.

## @pitlane/theme/dtcg API

- [@pitlane/theme/dtcg](https://pitlane.tools/package/theme/dtcg.md): Conversion between themes and W3C Design Tokens Community Group (DTCG) 2025.10 documents. [fromDTCG](https://pitlane.tools/package/theme/dtcg/function/fromDTCG.md) turns a DTCG document into the schema and token trees ["@pitlane/theme"!createTheme](https://pitlane.tools/package/theme/function/createTheme.md) accepts; [toDTCG](https://pitlane.tools/package/theme/dtcg/function/toDTCG.md) exports a theme back to DTCG, keeping values DTCG cannot express in a Pitlane extension.
- [fromDTCG](https://pitlane.tools/package/theme/dtcg/function/fromDTCG.md): Converts a W3C DTCG 2025.10 document into the schema tree and bare token tree ["@pitlane/theme"!createTheme](https://pitlane.tools/package/theme/function/createTheme.md) accepts.
- [toDTCG](https://pitlane.tools/package/theme/dtcg/function/toDTCG.md): Exports a compiled theme, a published theme component, or the init behind either one to W3C DTCG 2025.10 documents.
- [DTCGExport](https://pitlane.tools/package/theme/dtcg/interface/DTCGExport.md): DTCG documents exported from a theme.
- [DTCGThemeInit](https://pitlane.tools/package/theme/dtcg/interface/DTCGThemeInit.md): The runtime-shaped init [fromDTCG](https://pitlane.tools/package/theme/dtcg/function/fromDTCG.md) derives from a DTCG document.
- [PitlaneDTCGExtension](https://pitlane.tools/package/theme/dtcg/interface/PitlaneDTCGExtension.md): Pitlane's extension payload for a value DTCG cannot represent.
- [DTCGDocument](https://pitlane.tools/package/theme/dtcg/type/DTCGDocument.md): A JSON-compatible W3C Design Tokens Community Group document.

## @pitlane/theme/schema API

- [@pitlane/theme/schema](https://pitlane.tools/package/theme/schema.md): Token schemas: one factory per token type, plus `scale`, `any`, and `group`. Each factory returns a `remix/data-schema` schema tagged with the token type it declares, so the same value both validates a token and names the brand its accessor leaf carries.
- [any](https://pitlane.tools/package/theme/schema/function/any.md): A token with no type. Its value is emitted verbatim and its accessor leaf brands as a plain `string`, which the open-grammar CSS properties accept and the token-mapped longhands still reject.
- [border](https://pitlane.tools/package/theme/schema/function/border.md): A `border` token. Accepts CSS border shorthand text.
- [color](https://pitlane.tools/package/theme/schema/function/color.md): A `color` token. Accepts any CSS color, including `light-dark()`, `color-mix()`, and `currentColor`, plus DTCG's structured form.
- [dimension](https://pitlane.tools/package/theme/schema/function/dimension.md): A `dimension` token. Accepts any CSS length, including `clamp()`, `calc()`, `%`, and `em`.
- [duration](https://pitlane.tools/package/theme/schema/function/duration.md): A `duration` token. Accepts `ms`, `s`, and `calc()`.
- [easing](https://pitlane.tools/package/theme/schema/function/easing.md): A `cubicBezier` token, named for the CSS property it feeds. Accepts a four-number tuple or `cubic-bezier(…)` text.
- [gradient](https://pitlane.tools/package/theme/schema/function/gradient.md): A `gradient` token. Accepts CSS gradient function text.
- [group](https://pitlane.tools/package/theme/schema/function/group.md): A node that is itself typed and also carries per-child overrides. `self` applies to that node and to every descendant without its own entry; each key in `children` overrides it from there down.
- [number](https://pitlane.tools/package/theme/schema/function/number.md): A `number` token. Accepts a finite number, which is what unitless CSS values such as `line-height` and `opacity` take.
- [scale](https://pitlane.tools/package/theme/schema/function/scale.md): A dimension token whose accessor leaf is a multiplier rather than a value. The token emits its own custom property; the accessor leaf is callable, and carries the base itself as `.token`.
- [shadow](https://pitlane.tools/package/theme/schema/function/shadow.md): A `shadow` token. Accepts CSS shadow text, `inset` included.
- [stroke](https://pitlane.tools/package/theme/schema/function/stroke.md): A `strokeStyle` token, named for the CSS value it holds. Accepts a line-style keyword.
- [transition](https://pitlane.tools/package/theme/schema/function/transition.md): A `transition` token. Accepts CSS transition shorthand text.
- [SchemaGroup](https://pitlane.tools/package/theme/schema/interface/SchemaGroup.md): A schema group: per-child schemas, optionally under a schema for the node itself. [group](https://pitlane.tools/package/theme/schema/function/group.md) builds one; a plain object literal is the children-only form.
- [TokenSchema](https://pitlane.tools/package/theme/schema/interface/TokenSchema.md): A `remix/data-schema` schema that also names the token type it declares. Every factory in this module returns one.
- [SchemaNode](https://pitlane.tools/package/theme/schema/type/SchemaNode.md): A node in a schema tree.
- [font](https://pitlane.tools/package/theme/schema/variable/font.md): The two font token types, grouped because they share a prefix.

## @pitlane/vite-plugin-fetch-server API

- [@pitlane/vite-plugin-fetch-server](https://pitlane.tools/package/vite-plugin-fetch-server/index.md): 
- [fetchServer](https://pitlane.tools/package/vite-plugin-fetch-server/function/fetchServer.md): Serves `vite dev` requests through the Fetch handler an application's server module exports. Every request Vite does not answer itself goes to the current `default.fetch` of `entry`, loaded through the environment's module runner on each request, so an edit applies to the next request. Errors go to Vite's development error page.
- [FetchServerOptions](https://pitlane.tools/package/vite-plugin-fetch-server/interface/FetchServerOptions.md): Options for [fetchServer](https://pitlane.tools/package/vite-plugin-fetch-server/function/fetchServer.md).

## @pitlane/vite-plugin-remix API

- [@pitlane/vite-plugin-remix](https://pitlane.tools/package/vite-plugin-remix/index.md): The `remix()` Vite plugin — Remix 3 build orchestration, the `clientEntry()` island identity transform, dev serving through the app's fetch handler, hot module replacement for components and server-rendered data, prerendering, and a preview server, for any Vite or Vite+ project.
- [remix](https://pitlane.tools/package/vite-plugin-remix/function/remix.md): Wires Remix 3 into a Vite or Vite+ project: multi-environment builds (`dist/ssr` + `dist/client`) with an asset manifest for `createAssetResolver()`, portable `clientEntry(import.meta.url, …)` island identities that `render({ assets })` resolves, dev serving through the app's fetch handler, prerendering, and a preview server for the production build.
- [PrerenderConfig](https://pitlane.tools/package/vite-plugin-remix/interface/PrerenderConfig.md): The object form of the `prerender` option: which paths to render, plus how many to render at once and whether to follow the links they contain.
- [PrerenderContext](https://pitlane.tools/package/vite-plugin-remix/interface/PrerenderContext.md): What a `prerender` function receives.
- [RemixPluginOptions](https://pitlane.tools/package/vite-plugin-remix/interface/RemixPluginOptions.md): The options [remix](https://pitlane.tools/package/vite-plugin-remix/function/remix.md) accepts. Every one has a default, and most projects pass none.
- [PrerenderOption](https://pitlane.tools/package/vite-plugin-remix/type/PrerenderOption.md): Everything `remix({ prerender })` accepts: `true` for every static path in the route map, `false` for none, an explicit path list, a function that computes one, or a [PrerenderConfig](https://pitlane.tools/package/vite-plugin-remix/interface/PrerenderConfig.md) that adds `concurrency` and `spider`.
- [PrerenderPaths](https://pitlane.tools/package/vite-plugin-remix/type/PrerenderPaths.md): A function that decides which paths to prerender, for path sets that need async work — a CMS query, a filesystem scan, a database read.
- [PrerenderPathsOption](https://pitlane.tools/package/vite-plugin-remix/type/PrerenderPathsOption.md): The paths to prerender: `true` for every static path in the route map, an explicit list, or a function that computes one.

## @pitlane/vite-plugin-remix/hmr API

- [@pitlane/vite-plugin-remix/hmr](https://pitlane.tools/package/vite-plugin-remix/hmr.md): Browser-side half of server-data HMR. Import from `@pitlane/vite-plugin-remix/hmr` in the app's browser entry.
- [revalidate](https://pitlane.tools/package/vite-plugin-remix/hmr/function/revalidate.md): Applies a server update to the page: waits for initial hydration, then reloads the runtime's top frame, which refetches the current page through the app's fetch handler and reconciles it in place.