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

fumadocs-obsidian-md

v0.2.0

Published

Glue between remark-obsidian-md and Fumadocs: Vault resolver, slugs, MDX options and Asset URL handling

Readme

fumadocs-obsidian-md

Glue between remark-obsidian-md and Fumadocs: Vault resolver, slugs, MDX options and Asset URL handling.

Check for unparseable Frontmatter

fumadocs-obsidian-md-check [vault-dir]

Scans every Note (.md and .mdx, skipping dot-folders such as .obsidian) and names each one whose Frontmatter YAML cannot be parsed, with the parser's message. It exits non-zero if any Note fails, or if the Vault directory does not exist, and zero otherwise. Without an argument it reads VAULT_DIR, then falls back to public/vault.

Run it before the build so that a bad Note produces a readable message instead of a raw parser stack trace:

{
  "scripts": {
    "build": "fumadocs-obsidian-md-check && next build"
  }
}

The same scan is available programmatically as findUnparseableFrontmatter(dir).

Editing meta.json

fumadocs-obsidian-md/meta is a browser-safe module (no Node imports) that reads and writes a folder's meta.json: readMeta(text) gives { title, entries }, helpers (moveEntry, addSeparator, renameSeparator, removeSeparator, setTitle, createMeta) edit it, and writeMeta(existingText | undefined, meta) returns two-space JSON. Other keys and pages entries it does not model are kept in place.

The Fumadocs patch

Fumadocs parses a Note's Frontmatter at four entry points, none of which is guarded: the bundler loader, index generation, dynamic compile and includes. They run before any supported hook, so this package cannot intercept them, and one corrupt Note fails the whole build with a stack trace.

To make a corrupt Note render as plain Markdown instead (no Frontmatter), patch fumadocs-core's frontmatter function to catch the parse error. examples/fumadocs ships this as a pnpm patch (patches/[email protected], registered under patchedDependencies in pnpm-workspace.yaml). The patch is tied to the exact fumadocs-core version, so regenerate it when you upgrade.

Without the patch the check command is your safety net: it fails the build early and names the Notes to fix. With the patch the build succeeds, so keep running the check if you want to hear about corrupt Notes rather than have them silently lose their Frontmatter.

Both the patch and the check are workarounds. When Fumadocs ships a tolerant parser (or an error hook) upstream, delete the patch, and the check command may be removed.