💻 CLI

npx @getnarro/cli <command>

Install it globally (npm i -g @getnarro/cli) and the binary is narro.

npx narro resolves an unrelated package on npm. Use npx @getnarro/cli, or install globally and call narro.

Commands

Reference

Generated from the command tree, so it cannot disagree with narro --help.

narro analyze-slides-for-components

Analyze presentation slides to identify needed shared-ui components

narro build [file]

Build for production (pass a .md file for markdown mode)

narro bundle

Bundle presentation into a single self-contained HTML file

narro capture-website <url>

Capture a full-page screenshot of a website

narro check <file|dir>

Validate a markdown deck, or measure built output with —fit

narro comments

Manage slide comments

narro create [project-name]

Create a new Narro presentation project

narro create-template-from-screenshots [template-name]

Generate a template from presentation screenshots using AI

narro dev [file]

Start development server (pass a .md file for markdown mode)

narro export [file]

Export presentation to static files, PPTX, or Google Slides

narro fmt <file>

Normalise a deck’s whitespace and frontmatter without changing what it renders

narro import <source>

Import presentation from PowerPoint or Google Slides

narro new <file>

Scaffold a starter markdown deck

narro preview

Preview built presentation

narro themes

Browse and apply themes from the marketplace

Notes

check is the CI gate. narro check deck.md --strict promotes warnings to errors and exits non-zero, which is the step a pipeline runs — the scaffolded markdown templates map their lint script to exactly that. Plain check exits 0 on warnings, which makes it the right form for the edit loop and the wrong form for CI.

Three flags, three different questions:

See Verifying a deck for what each of these sees and does not see.

narro build <deck>.md measures fit for you. A single-file deck has no package.json to wire a check into, so the build runs one: it reports the overflow and exits non-zero. A machine with no browser gets a warning rather than a failure — narro check dist --fit is the strict form — and --no-fit turns it off entirely. This is the only fit check a narro new deck gets, because it is the only place there is to put one.

--fit and React mode. check is markdown-only, but --fit measures built output: npm run build && npx @getnarro/cli check dist --fit works for a React deck and is the only fit check either mode has. Every React template ships a fit script that runs exactly that. It needs Chromium (npx playwright install chromium); without one it fails, because a check that measured nothing is not a check that passed. --fit-if-available makes that a warning when you want it to be one, and NARRO_CHROMIUM=/path/to/chromium points it at a browser your image already has.

Formatting. Use narro fmt, not Prettier — a markdown formatter can reflow a paragraph and move an attribute block onto its own line, which changes what it styles with nothing to report it. See Formatting a deck.

Scaffolding. npm create narro@latest my-deck and narro create my-deck run the same code. narro new deck.md is different: it writes a single markdown file with no project around it.

Markdown mode. Passing a .md file to dev or build switches to markdown mode, where no project or config file is needed — the CLI brings its own runtime.

Export fidelity. A static build keeps animations, embeds, and live components working. PPTX maps slides onto real PowerPoint shapes so text stays editable, but anything driven by a live component becomes its rendered state. PDF flattens fragments to their final state.

Credentials. Google Slides import and export need Google OAuth credentials in the environment. create-template-from-screenshots and analyze-slides-for-components call a hosted vision model and need ANTHROPIC_API_KEY or OPENAI_API_KEY.