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

generate-guidebook

v2.0.0

Published

A utility for generating a tutorial guide. Used in:

Readme

Generate Guidebook

A utility for generating a tutorial guide. Used in:

  • https://javascript.express
  • http://react.express
  • http://www.reactnativeexpress.com/

Example

const generateGuidebook = require('generate-guidebook')

const guidebook = generateGuidebook('./pages')

Next plugin

const withGuidebook = require('generate-guidebook/next')

// These are the default options
module.exports = withGuidebook({
  guidebookDirectory = './pages',
  guidebookModulePath = './guide.js',
})

Directory structure

  • The root of your guidebook must contain an index.mdx file. This is the root page.
  • At any level, a folder is treated as a documentation page if it contains an index.mdx inside it. The folder name becomes the slug segment.
  • Regular pages are .mdx files that sit alongside folders (excluding index.mdx).

Example:

pages/
  index.mdx              -> slug: ""
  getting-started/
    index.mdx            -> slug: "getting-started"
    install.mdx          -> slug: "getting-started/install"
  guides/
    index.mdx            -> slug: "guides"
    deep-dive/
      index.mdx          -> slug: "guides/deep-dive"
      advanced.mdx       -> slug: "guides/deep-dive/advanced"
  faq.mdx                -> slug: "faq"

Notes:

  • Backwards compatibility: the older pattern of foo.mdx alongside a foo/ folder (when the folder has no index.mdx) still works. The recommended pattern is foo/index.mdx.
  • Ordering: control ordering via either frontmatter order or a config.json file placed in the directory.
    • config.json takes precedence over frontmatter order.
    • In config.json, list basenames: for directory pages use the directory name (e.g. "guides"), and for file pages use the file basename without extension (e.g. "faq").
    • Example config.json:
      { "order": ["getting-started", "guides", "faq"] }
  • Hiding pages: add hidden: true in a page's frontmatter to omit it from the tree. You can also set hidden: SOME_VARIABLE and pass variables to conditionally hide.