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

@quiescent/wiki

v0.0.1

Published

Astro-focused wiki toolkit: Obsidian-style wikilinks, tag index, search, and note graph over a directory of markdown, built at build time for Cloudflare Workers or Node

Readme

@quiescent/wiki

Astro-focused wiki toolkit over a directory of markdown notes: Obsidian-style [[wikilinks]], hierarchical tags, client-side search, and a force-directed note graph. Everything is computed at build time and baked into the bundle, so the same code runs on Cloudflare Workers (no runtime filesystem) and Node.

Pairs with @quiescent/server + @quiescent/editor for in-browser editing that persists through a git forge; see the repo root README and docs/.

Wiring

// astro.config.mjs
import { quiescentWiki } from "@quiescent/wiki";

export default defineConfig({
  integrations: [quiescentWiki({ dir: fileURLToPath(new URL("../wiki", import.meta.url)) })],
});

The integration:

  • registers a remark plugin rewriting [[Target]] / [[Target|alias]] into links (.wikilink, dead links become .wikilink--dead spans and warn);
  • exposes virtual:quiescent-wiki with build-time data:
/// <reference types="@quiescent/wiki/virtual" />  // in env.d.ts
import { searchIndex, graph, tags, notes } from "virtual:quiescent-wiki";

| Export | What it is | | --- | --- | | searchIndex | Serialized MiniSearch index (title/tags/headings/body) | | graph | { nodes, edges } — notes + tags, wikilink + membership edges | | tags | Record<tag, {url, title}[]> for tag pages | | notes | Note metadata (frontmatter, headings, excerpt — no body text) |

Serve searchIndex/graph from auth-guarded API routes (Cache-Control: private) and consume them with the client module:

import { fetchWikiSearch, mountWikiGraph } from "@quiescent/wiki/client";

const search = await fetchWikiSearch("/api/wiki/search-index");
search.search("hydroponics");

mountWikiGraph(document.getElementById("graph")!, graph, { showTags: true });

Copyable route + page examples live in code/web/src/pages/wiki-demo/ and code/web/src/pages/api/wiki/ in this repo.

Node API

All build-time (uses node:fs) — never import from client islands:

  • scanNotes({ dir }) → parsed notes (frontmatter, tags, headings, excerpt, stripped text, wikilink targets)
  • buildWikiIndex({ dir }) → name/title → URL index with ambiguity tracking
  • resolveWikiTarget(target, index) → URL or null (dead/ambiguous)
  • buildWikiGraph(index, { includeTags }), buildTagIndex(index)
  • buildSearchIndex(index) → serialized MiniSearch (SEARCH_OPTIONS shared with the client loader)
  • validateWikiLinks({ dir }) / reportWikiLinks({ dir }) — dead-link CI gate:
// scripts/check-wiki-links.ts
import { reportWikiLinks } from "@quiescent/wiki";
process.exit(reportWikiLinks({ dir: new URL("../../wiki", import.meta.url).pathname }));

Note URLs are the wiki-relative path with each segment github-sluggered — exactly the id Astro's glob content loader computes, so wikilink hrefs line up with getCollection-driven routes.

Content conventions

See docs/conventions.md in the repo root: frontmatter (title, type, status, tags, created, updated), hierarchical namespace/value tags, one note per file, sources as sources/<date>-<slug>/source.md resolving by frontmatter title.