Skip to content
packages

Packages

Deep reference for every @docvia/* package: what each one does, where it runs, and every export.

On this page

docvia ships as eight packages. Two hold almost everything, split by where the code runs; the rest are the command line, search and the plugins with heavy dependencies. This section is the API reference for each one. For task-oriented walkthroughs, see the Guides.

PackageRunsWhat it is
@docvia/coreAnywhere: Workers, browsers, NodeConfig and plugin API, the IR, Markdown parsing, rendering, sources, SSR, and the React and Svelte bindings. No Node APIs.
@docvia/buildNode, at build timeThe compiler, the page pipeline, config file loading, and the Vite and Next.js plugins.
@docvia/cliNodeThe docvia command (init, build, dev, sync, preview).
@docvia/searchAnywhereSection-level Orama indexing and the client search helper.
@docvia/markdownAnywhere, any appA dependency-free Markdown renderer with streaming for AI output. Needs nothing else from docvia.
@docvia/plugin-shikiBuild timeSyntax highlighting via Shiki.
@docvia/plugin-mermaidBuild timeMermaid fences as diagram components.
@docvia/plugin-openapiBuild time, plus a Workers-safe proxyAPI reference pages from an OpenAPI spec.

An app usually installs two of them:

pnpm add @docvia/core @docvia/search
pnpm add -D @docvia/build @docvia/plugin-shiki

@docvia/core

Each area is a subpath, so an app only bundles what it imports.

@docvia/build