Skip to content
Reed Docs

reed dev

Live preview while you edit.

sh
reed dev [--dir <path>] [--content <path>] [--port <n>] [--strict-tokens] [--strict-components]

Starts a local preview server that rebuilds as you edit docs.json and your content.

Prerequisites: a prior successful reed prefetch on this machine, and a Corepack-resolvable package manager. Given those, dev needs no network.

Options

Section titled “Options”
--dirpath

Project root. Defaults to the current directory.

--contentpath

Content directory. Defaults to <dir>/content.

--portinteger

Port to listen on.

--strict-tokensbooleandefault: false

Escalate every warning except DS-D* to an error.

--strict-componentsbooleandefault: false

Escalate DS-D* design-system warnings to errors.

What dev does not produce

Section titled “What dev does not produce”

dev renders pages. It does not write the build-only outputs: no llms.txt, no markdown mirrors, no sitemap.xml, no robots.txt, no _headers. The <head> link and footer link that point at llms.txt are absent under dev too, since there would be no file for them to point at.

If you are working on a derived surface rather than on pages, run reed build and inspect the output directory — dev cannot show you those.

Sharing one compile path

Section titled “Sharing one compile path”

dev compiles through the same path as check and build, so a page that renders in dev renders in build. The difference is which outputs get written, not how the content is interpreted.