> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meow.style/llms.txt
> Use this file to discover all available pages before exploring further.

# Built-in modules

> The meow: namespace — first-party modules that ship inside the binary.

meow ships a small set of first-party modules under the **`meow:`** namespace.
They're baked into the binary — there's nothing to install, and they're available
in both [runtime modes](/concepts/modes).

<CardGroup cols={3}>
  <Card title="meow:http" icon="server" href="/api/http">
    A Web-standard HTTP/1.1 server. `serve()` a `Request → Response` handler.
  </Card>

  <Card title="meow:ui" icon="palette" href="/api/ui">
    Print on-brand status lines — `purr`, `hiss`, `pounce`.
  </Card>

  <Card title="meow:test" icon="vial" href="/api/test">
    The test runner API — `test()` and `expect()`.
  </Card>
</CardGroup>

## Importing

```typescript theme={null}
import { serve } from "meow:http";
import { ui } from "meow:ui";
import { test, expect } from "meow:test";
```

Types resolve in your editor automatically — `meow sync` writes the `meow:*`
declarations into `.meow/types/meow/`, and the generated `tsconfig` maps the
`meow:*` specifier to them. No `@types` packages, no install step.

<Note>
  These modules are authored in TypeScript inside the runtime and are the single
  source of truth for both their behavior and their published type declarations —
  so the docs, the types, and the implementation never drift.
</Note>

<Tip>
  Node built-ins live under the standard `node:` namespace (`node:fs`, `node:path`,
  …) and are available in [`node-compat`](/runtime/node-compat) mode. The `meow:`
  namespace is for meow's own first-party surface.
</Tip>