npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

deckdown

v1.2.2

Published

Markdown presentation engine for AI agents with deterministic PDF, PNG, and PPTX output

Readme

DeckDown

Markdown to presentation engine, open source and local.

DeckDown is a local-first, open source Markdown-to-presentation engine for teams that want readable source files, a real localhost Studio, and deterministic output to PDF, PNG, and PPTX.

It is built for repo-native slide workflows. Write in Markdown, keep themes and shared sections in source control, review changes as text, and render the same deck into review assets or handoff files without switching tools.

Install

npm install -g deckdown@latest

One-off use without a global install:

npx deckdown@latest --help

Published package:

  • npm: https://www.npmjs.com/package/deckdown

Quick Start

Scaffold a workspace:

deckdown init .
deckdown init . --template paper-letter

Open the localhost Studio:

deckdown studio .

Create a first deck:

---
title: Product Review
theme:
  colors:
    background: '#ffffff'
    text: '#111827'
    heading: '#0f172a'
    accent: '#2563eb'
    codeBg: '#f8fafc'
---

# Product Review

DeckDown compiles Markdown slides to real presentation files.

---

# Same Source, Multiple Outputs

- PDF for review
- PNG for visual QA
- PPTX for downstream handoff

Render it:

deckdown deck.md -o deck.pdf
deckdown deck.md -o slides --format png
deckdown deck.md -o deck.pptx --format pptx

Why DeckDown

  • Repo-native authoring: keep decks in git, split shared content into Markdown or YAML, and review changes as source instead of opaque slide binaries.
  • Local Studio: edit and review on localhost with a file tree, live preview, diagnostics, docs, and export controls in one workflow.
  • Real render pipeline: Mermaid and LaTeX survive the actual preview and export path instead of stopping at a mock browser view.
  • One source, multiple deliverables: generate PDF, PNG, and PPTX from the same Markdown deck.
  • Open and inspectable: no hosted editor requirement, no hidden project state, no lock-in around the authoring surface.

Showcase

Showcase source:

Studio

DeckDown Studio is a localhost editing and review surface for the same source files you keep in the repository.

Current Studio workflow includes:

  • CodeMirror-based Markdown editing
  • DeckDown-aware snippets and completions
  • inline diagnostics while typing
  • file-tree workspace navigation
  • active-slide outline
  • local docs browser
  • asset preview
  • keyboard shortcuts and saved layout preferences
  • template bootstrap for empty workspaces

Studio is not a separate document model. It operates directly on the repo files.

Mermaid And LaTeX

DeckDown supports both Mermaid and display-style LaTeX math blocks in the preview and export pipeline.

Mermaid:

```mermaid
graph TD
  Draft --> Review --> Export
```

LaTeX:

$$
\int_0^1 x^2 \, dx = \frac{1}{3}
$$

These blocks render through the same local path used for Studio, PDF, PNG, and PPTX output.

Output Formats

| Format | Output | Best for | | --- | --- | --- | | PDF | single file or stdout | approvals, review, archival | | PNG | directory of slide images | README embeds, QA, visual diffs | | PPTX | single file | downstream PowerPoint handoff |

Documentation

| Guide | Use it for | | --- | --- | | Docs Overview | start here and navigate the docs set | | Getting Started | install DeckDown and render your first deck | | CLI Reference | learn commands, flags, and output behavior | | Authoring Guide | work with frontmatter, imports, images, and layout attributes | | AI Agent Workflows | fit DeckDown into agent-driven content pipelines | | AI Instructions | reuse canonical AGENTS.md guidance |

Example Decks

Requirements

| Task | Requirement | | --- | --- | | Run DeckDown | Node.js >= 18 | | Generate PNG | Ghostscript (gs) on PATH | | Run npm run release-check | gs, pdftoppm, and LibreOffice soffice |

Current limits:

  • images are expected to be local files
  • --watch is not implemented

Release Verification

Before publishing, run:

npm run release-check

The release gate verifies:

  • Jest suites
  • sample PDF, PNG, and PPTX rendering
  • packed CLI behavior
  • npm packaging contents

Development

npm install
npm test -- --runInBand
npm run release-check

License

MIT