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

@domphy/press

v0.22.0

Published

Domphy Press — VitePress-baseline static doc site framework built on @domphy/app + @domphy/markdown

Downloads

3,203

Readme

@domphy/press

domphy.com · Docs · npm

A VitePress-baseline static documentation site framework built on @domphy/app and @domphy/markdown. Write docs in Markdown, get a fast static site with Domphy-native CSS-in-JS theming — no separate stylesheet to maintain.

Features

  • VitePress-compatible Markdown — containers (tip/warning/danger/info), code-group tabs, <<< file imports, !!!include(path)!!! file includes, GFM task lists, mark/sub/sup
  • Shiki syntax highlighting — line highlighting, diff annotations, focus groups, copy button
  • Automatic dark mode — via themeCSS() + pressCSS() CSS vars; no flash of unstyled content
  • Built-in local search — client-side JSON index, no server required
  • Full navigation — top nav, sidebar with collapsible groups and badges, TOC aside, prev/next links
  • Extras — announcement bar, social links, edit link, last-updated (from git), reading time, heading anchors, mermaid diagrams, i18n locale routing

Install

npm install @domphy/press

Peer dependencies: @domphy/app, @domphy/core, @domphy/markdown, @domphy/theme, @domphy/ui.

Quickstart

Create press.config.ts:

import { defineConfig } from "@domphy/press"

export default defineConfig({
  title: "My Docs",
  description: "Documentation for my project.",
  base: "/",
  hostname: "https://example.com",
  srcDir: "docs",
  outDir: "dist",
  themeConfig: {
    nav: [{ text: "Guide", link: "/guide/" }],
    sidebar: {
      "/guide/": [{ text: "Getting Started", link: "/guide/" }],
    },
  },
})

Build and preview:

npx domphy-press build
npx domphy-press preview

CLI

| Command | Description | |---|---| | domphy-press build | Build static site to outDir | | domphy-press dev | Dev server with live rebuild on Markdown changes | | domphy-press preview | Preview the pre-built output |

Programmatic API

import { buildSite, renderDoc, defineConfig, createHighlighter, pressCSS } from "@domphy/press"

// Build full site
await buildSite({ config, srcDir, outDir })

// Render a single Markdown file → DomphyElement[]
const highlight = await createHighlighter()
const result = await renderDoc("# Hello\n\nContent.", { filePath, docsDir, repoRoot, highlight })
// result.body / result.toc / result.frontmatter / result.title

// Get global CSS to inject in <head>
const css = pressCSS()

// Start a dev server
import { startDevServer } from "@domphy/press"
const { server, notify } = startDevServer(outDir, 3000)

The ./browser subpath exports the client-side island runtime (search widget, layout shells) for Vite/browser bundles — no Node.js built-ins.

See the full docs for configuration reference, Markdown features, routing, search, i18n, and deployment guides.