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

@helpnest/mintlify

v0.1.1

Published

Migrate Mintlify docs to HelpNest

Readme

@helpnest/mintlify

Migrate your Mintlify docs into HelpNest — the open-source customer help center.

Reads your mint.json navigation, converts MDX pages to Markdown, and creates the equivalent Collections and Articles in HelpNest. Supports filtering by section and a dry-run preview mode.

Installation

npm install -g @helpnest/mintlify
# or run directly
npx @helpnest/mintlify <command>

Prerequisites

A HelpNest API key — generate one from your HelpNest dashboard under Settings → API Keys.

Setup

cp .env.example .env
# Edit .env with your HelpNest credentials

Commands

preview

Preview what would be migrated without touching HelpNest:

npx @helpnest/mintlify preview --docs-dir ./my-docs

Output:

Mintlify project: "Acme Docs"

Collections to create:
  Getting Started — 4 article(s)
  Guides — 8 article(s)
  API Reference — 12 article(s)

Total: 24 articles across 3 collections

migrate

Migrate the full project:

npx @helpnest/mintlify migrate \
  --docs-dir ./my-docs \
  --helpnest-url https://help.yourcompany.com \
  --helpnest-key hn_live_xxx \
  --workspace your-workspace-slug

Flags:

| Flag | Description | |------|-------------| | --docs-dir <path> | Path to your Mintlify project root (where mint.json lives) | | --helpnest-url | Your HelpNest base URL | | --helpnest-key | HelpNest API key | | --workspace | HelpNest workspace slug | | --dry-run | Preview without creating anything | | --collections-only | Create collections only, skip articles | | --group <name> | Only migrate pages from a specific nav group (partial match) |

How it works

  1. Reads mint.json — parses the navigation structure to discover all pages and group them into Collections.
  2. Loads MDX files — reads each .mdx or .md file from disk.
  3. Strips MDX syntax — removes JSX components, import/export statements, and converts Mintlify-specific components (<Callout>, <Note>, etc.) to Markdown blockquotes.
  4. Creates Collections — one HelpNest Collection per top-level nav group.
  5. Creates Articles — one HelpNest Article per page, linked to its Collection.

What gets migrated

| Mintlify | HelpNest | |----------|----------| | Top-level nav group | Collection | | .mdx / .md page | Article | | title frontmatter | Article title | | description frontmatter | Article excerpt | | Page content (MDX → Markdown) | Article body |

What doesn't migrate

  • API reference pages with OpenAPI/Swagger specs (content is preserved as text but not rendered as an API reference)
  • Custom MDX components beyond the built-in Mintlify ones
  • Images (referenced by their original relative paths — update them manually after migration)
  • tabs in mint.json (pages under tabs are still migrated, but the tab structure becomes flat collections)

Contributing

PRs welcome! See CONTRIBUTING.md.

License

MIT © HelpNest Contributors