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

bunt

v0.0.1

Published

A tool for creating web components using the npm packaging system and browserify - for sweet as sweet can be re-use and encapsulation.

Downloads

5

Readme

Bunt - a minimalist bundling method for client-side JavaScript

This is a pre-alpha project for bringing some peace, sanity and pragmatism to client-side JavaScript. It's right in the same playing field as projects like component, grunt, yeoman, bower, browserify, etc.

After observing the development of these tools and listened to the colorful and ongoing debate, I've come to believe in the following principles:

  1. Reproducability - a module that can be built and used at one point in time must never be broken or has its behavior changed because its dependencies change.
  2. Encapsulating nested dependencies. Multiple versions of the same dependency - even if not desired - must be able to co-exist in a single bundle. This is the only way of solving certain dependency problems.
  3. Minimal restrictions Allow for all kinds of compile-to-JS languages, pre-processed CSS, etc. For each requirement that is enforced by a bundling system, a certain part of the developer community is excluded. This is undesirable.
  4. Minimal external surface Similarly to 3., using the bundled components must impose very little on the user and his/her site. It should be as simple as including one JavaScript file and a stylesheet.

To create a system that conforms to these principles, one needs

  1. a package manager
  2. a tool that bundles JavaScript
  3. something that ties 1. and 2. together

As I believe in inventing as little as possible, Bunt solves only 3. and uses npm for package management and browserify for bundling.

Todo

  • Flesh out this document in more detail