> ## Documentation Index
> [HTML page](https://blode.md/docs/features/dev-server)
> [Documentation index](https://blode.md/docs/llms.txt)
> Use the index to discover all available pages before exploring further.

# Local development

Run edda dev to preview your documentation locally at localhost with hot reload, matching the deployed site as you edit MDX and docs.json.

The `edda dev` command starts a local preview server that renders your documentation exactly as it appears when deployed. Changes to your content and configuration are reflected in real time.

## Start the dev server

```bash
edda dev
```

This starts the server at `http://localhost:3030` and opens it in your default browser.

## Options

- `--no-open` (type: boolean, default: false): Do not open the browser automatically on start.

### Examples

```bash title="Custom port"
edda dev -p 4000
```

```bash title="Specific directory"
edda dev -d ./my-docs
```

```bash title="No browser"
edda dev --no-open
```

## How file watching works

The dev server watches your content directory and reloads automatically when files change.

| Change type         | Behavior                                                      |
| ------------------- | ------------------------------------------------------------- |
| MDX content edit    | Incremental update. Only the affected page is re-rendered.    |
| `docs.json` edit    | Full reload. Navigation, branding, and all pages are rebuilt. |
| New or deleted file | Incremental update. Navigation is refreshed automatically.    |

> [!INFO]
> File changes are debounced with a 100ms delay to batch rapid edits into a
>   single reload.

## Ignored directories

The file watcher skips these directories to avoid unnecessary reloads:

- `.git`
- `.next`
- `dist`
- `node_modules`

> [!TIP]
> The dev server runs the full blode.md rendering engine locally. What you see
>   in the browser matches your deployed site, including search, navigation, and
>   component rendering.