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

@blogmcp/nav-core

v0.2.1

Published

Framework-agnostic navigation tree core — types, validation, traversal, and immutable mutations for the KB information-architecture (menu) layer. Zero framework dependencies; consumed by the API service, MCP tools, and the blog SDK.

Readme

@blogmcp/nav-core

Framework-agnostic core for the KB navigation (menu) tree. Pure TypeScript — no I/O, no framework. The design lives in competitor-monitor/docs/internal/navigation-model.md.

This package is the shared logic surfaced two ways: the SDK runs it in-memory over a cached tree, and the server exposes it as MCP/API tools. Mirrors the @blogmcp/mdx-schema → renderer split.

Modules

| Import | Contents | |---|---| | @blogmcp/nav-core | everything (barrel) | | @blogmcp/nav-core/types | node model: NavNode union, NavTree, FlatNode, LocalizedNode | | @blogmcp/nav-core/validate | validate(tree, opts) / assertValid — cycles, depth, dangling refs, single-owner, data-bag caps | | @blogmcp/nav-core/traverse | findNode, breadcrumbs, getSiblings, getNextPrev, getSubtree, flatten (FLAT), localize, prune, sortTree | | @blogmcp/nav-core/mutate | insertNode, removeNode, moveNode, reorderChildren — immutable; throw NavMutationError |

Invariants

  • Immutable: traversal and mutation never edit inputs; mutations return new trees.
  • Server-authoritative: the API re-runs validate() after every mutation.
  • Opaque data: the data bag is never interpreted, only size/depth-capped.
  • Single multilingual tree: labels is a per-locale map; localize() resolves to one locale with fallback + an optional labelResolver (article titles come from the consumer — nav-core does not know article content).

Not here yet

The content→default-tree auto-builder and the auto-build ⊕ overrides merge ship with the API service slice (they need the article content index and the auto-append policy — see navigation-model.md §9).

Scripts

npm test --workspace=@blogmcp/nav-core        # vitest
npm run build --workspace=@blogmcp/nav-core   # tsc → dist