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

propolis

v0.3.18

Published

A simple blog platform, written in Preact

Readme

propolis

Run on Repl.it

A simple blog platform, written in Preact.

Renders Markdown using highlight.js for syntax highlighting.

installation

In your project, include the following scripts:

  <head>
    <link rel="stylesheet" type="text/css" href="https://cdn.jsdelivr.net/npm/[email protected]/build/highlight.css" />
    <link rel="stylesheet" type="text/css" href="https://cdn.jsdelivr.net/npm/[email protected]/build/main.css" />
  </head>

  <body>
    <script src="https://cdn.jsdelivr.net/npm/[email protected]/build/main.bundle.js"></script>
    <script src="https://cdn.jsdelivr.net/npm/propolis/build/vendors~highlight.js.bundle.js"></script>
  </body>

configuration

In the root of your web directory, create a pages.json manifest file which tells propolis where to find and route your content.

The file has the the following format:

  [
    // normal page
    {
      "name": string       // displayed on navbar
      "id": string         // the route for this page
      "filepath": string   // the path to a markdown file on the server
    },
    // Posts page
    {
      "name": string,
      "id": string,
      "posts": []            // Array of normal pages
    },
  ]

For example,

[
  {
    "name": "Home",
    "id": "", // empty string means index route
    "filepath": "home.md"
  },
  {
    "name": "Posts",
    "id": "posts",
    "posts": [
      {
        "name": "Hello World Post",
        "id": "hello-world",
        "filepath": "posts/hello.md"
      }
    ]
  },
  {
    "name": "Projects",
    "id": "projects",
    "filepath": "projects.md"
  }
]

styling (optional)

app-level

Include a css file to overwrite any rules included here and add your own styling.

highlight.js

You can find themes for highlight.js here.