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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@jhpriestley/palimpsest

v0.5.3

Published

Palimpsest ==========

Readme

Palimpsest

Palimpsest is a new web framework which takes a fresh approach to some of the longstanding conventions of the genre.

Instead of "routes" which run arbitrary code, Palimpsest divides an application into "inputs", "folds", "outputs", and "views". An "input" is more or less a dumb bucket for user input. A fold transforms that raw data into useful formats. An output provides a live readout of user-customized data from one or more folds. And a view shows output data to the user, and sends user input to inputs.

Why organize things in this way? Because inputs are a raw data record, they can be reused as a program evolves to serve different purposes. Because folds are an immutable summary of inputs, rather than an imperative "action" effecting database state, they can be rerun at will. Because outputs are a live event stream, Palimpsest applications are live by default, with no extra effort required to make reactive widgets like chat. Because Palimpsest stores its data as immutable records in a key-value store, rather than mutable database tables, caching can be done correctly without constant programmer input and effort.

Comprehensive documentation is on the way, but for now you can find examples within the example directory, and some explanatory content at my blog.