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

gastona

v0.9.11

Published

buildtool for vigour-io

Downloads

11

Readme

Gaston - the return of the King

(check the README in the master branch for feature list and roadmap)

Installing
$ git clone [email protected]:vigour-io/gaston.git
$ cd gaston
$ git checkout new-gaston
$ npm install
# BEWARE - running the next line will replace the current gaston as a system CLI
$ npm install -g .
Usage
# go to any folder, for example:
$ cd development/vigour-js
# run it
$ gaston

now you can fire up a browser window and open: http://localhost:8080

Features ready

  • run gaston from any path and you'll get a webserver
  • directory index navigation
  • serves static files
  • opening an .html file will
    • render the page
    • run separate watchers for js and less files

Roadmap

  • set up browserify and less compilation
  • start adding params to configure options
  • create javascript API so it can be used as a module

Some notes

Convention over Configuration

Let's not try to get too religious, but there are things that simply work better if we agree upon them; This will allow us to get rid of overhead such like the require('style.less') and the hacking we need to add to browserify.

  • CSS - Less will compile from the file style.less to bundle.css
    • style.less can have @imports to files in styles dir, to make it more modular
    • it can also have Less code in the file
    • production build will generate bundle.min.css
  • JS - Browserify will compile from the file index.js to bundle.js
    • index.js is the entry point
    • can contain all the logic or be split into smaller modules
    • production build will generate bundle.min.js