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

@jakubro/folio

v0.3.0

Published

Serve a folder of markdown to the browser, updating a page only when its own file changes.

Downloads

619

Readme

folio

License: GPL v3 Version Status

A live view of a folder of markdown and data. Point folio at a folder and read it in your browser: every page rendered with GitHub-flavoured markdown, math, highlighted code and diagrams, every page current the moment you save it, and the folder known as a whole - what you have not read yet, which figures no longer match their data, what links where and what is broken.

Try it

npx @jakubro/folio ~/notes

Open the address it prints: http://localhost:8640/, or the next free port when that one is taken. folio needs Node.js 22.18 or later; npm install --global @jakubro/folio keeps it installed as folio.

Why folio

A markdown previewer shows you one file. folio keeps a model of the whole folder, so it can tell you about it:

  • What is new to you. folio remembers what you have read. Reopen a page and every block added, changed or removed since is marked - a table by its rows, a list by its items, code by its lines - the old wording a click away, and the tree points at every document that moved.
  • Data, live in your documents. CSV, JSON, Parquet, SQLite and other data files open as tables and trees, with each column's spread under its header and, for any filter, what sets its records apart from the rest. A document embeds a table, a chart or a single value from them, or a SQL query across them, and each one redraws when its data changes.
  • Figures that check themselves. Tie a number in your prose to the data it quotes, and folio flags it the moment the data disagrees.
  • A folder that keeps its own rules. Declare kinds of documents and rules as queries in a FOLIO.md. One health view - and folio check in CI - lists every broken link, missing include, failing query and broken rule.
  • History of everything. Every version git holds, merged with the saves folio saw, compared block by block, and digests of any day or week.
  • Agents and editors read it too. An MCP server, a JSON API and a language server give them the same model you read, and an agent skill teaches agents to write documents that use it.

The folder stays plain markdown: every page still reads on GitHub, and folio writes into it only what a FOLIO.md asks for.

Learn more

Full documentation is published at jakubro.github.io/folio.

  • Guide - every view folio adds, with pictures
  • Reference - every option, address, key and rule, and what folio reads and writes
  • Architecture - how folio works and why, for contributors

License

Copyright (C) 2026 Jakub Roman. Distributed under the GNU GPL v3.