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

redrunner

v0.11.3

Published

A tiny framework with legs

Readme

RedRunner

A small JavaScript framework with legs.

Overview

RedRunner is a JavaScript framework for building dynamic pages and apps.

It is in early development and not ready to use.

Demo

There is a very minimal demo app, which you can run like so:

git clone [email protected]:andyhasit/redrunner.git
cd redrunner/demo
npm i
npm run start

You can also inspect the bundle size:

npm run build-prod
gzip dist/main.js
ls -lh dist

Installation

Quick start

For new projects use the demo as a starting point. For existing projects you can copy the relevant parts from package.json and webpack.config.js into your project.

Alternatively, you can install RedRunner manually with npm and follow the rest of the instructions here.

npm i -D redrunner

This will install redrunner and a compatible version of babel-plugin-redrunner.

Babel configuration

You must include the following plugins in this order in your babel configuration:

"plugins": [
  ["babel-plugin-redrunner"],
  ["@babel/plugin-proposal-class-properties"]
]

The babel-plugin-redrunner transforms parts of your code and is required for RedRunner to work.

Bundling

I recommend using webpack instead of alternatives as it gives you better control over source maps, which really helps for development.

Source maps

The babel plugin replaces each component's __html__ field with generated code, and debugging is a lot easier if you can see that generated code.

With webpack you can set the config's devtools to something like 'eval-cheap-source-map' which makes the source maps show the transformed code, but preserves the module separation which is nice. However this will include all transformations, so if you're transpiling to ES5 (which you probably do using a preset) then it will make it harder to track your own code.

One solution is not transpile to ES5 during development, meaning the only transformations you'll see are RedRunner's, which makes debugging a lot nicer.

The demo's webpack.config.js file shows one way to achieve this.

You can read more about webpack's devtools option here.

User Guide

This is coming, but so is Christmas.

Contributing

Contributions welcome, see the main repo.

License

MIT