mdv debug

Authoring and plugin diagnostics.

Diagnostic mode. Do not touch the glowing panels unless the manual says so.

Usage

mdv debug <command> [options]

mdv debug plugin

Validate a plugin package against mediva's enforced manifest shape.

Usage

mdv debug plugin <module-or-path>

Arguments

  • <module-or-path> — A package directory, module file, or bare package name.

Examples

mdv debug plugin ./my-plugin   # self-check a plugin package

mdv debug fences

Compile every mdv fence and *.mdv.md corpus template under the given paths against its owning plugin registry.

Usage

mdv debug fences [paths...] [-f FORMAT]

Arguments

  • [paths...] — Files or directories to scan; default: packages.

Output

  • -f, --format FORMAT — stylish (default) or json.

Examples

mdv debug fences docs   # compile every mdv fence under docs/

mdv lsp

Run the language server over stdio (what editors invoke).

Configuration

mediva.config.mjs: what blocks, per-path severity overrides, and plugins.

On this page

Usagemdv debug pluginUsageArgumentsExamplesmdv debug fencesUsageArgumentsOutputExamples