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 🙏

© 2024 – Pkg Stats / Ryan Hefner

dumpster-fire

v0.1.3-pre.2

Published

<div style="text-align:center"><img src ="https://user-images.githubusercontent.com/4172067/33363981-5df42498-d497-11e7-805c-78cc6b1dd9d6.jpg" width=500/></div>

Downloads

7

Readme

dumpster-fire Build Status

Image used with permission from Maggie Appleton and Egghead.io

This is a personal hobby project. Until (unless) this notice is removed, you shouldn't take it seriously or use it in production. This is simply an experiment in how fast I can make very large builds. Currently dumpster-fire is riddled with bugs and inconsistencies, and until I decide on a long term plan it'll likely stay that way.

Why the name dumpster-fire?

The name really serves two purposes. The first is to highlight the current state of bundling JavaScript. The second purpose is to highlight the fact that you really shouldn't be using this library for production (for real).

If this project is successful will you change the name?

Maybe. Probably not if I can help it. I like the name, it makes me giggle.

Isn't this where the documentation is supposed to go?

Yup, but it's way too early in the project to pretend like I've got any of the api nailed down. If anything comes of this, I promise to improve the documentation.