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

pyre

v0.0.29

Published

Highly opinionated application template and build process.

Downloads

57

Readme

#pyre A highly opinionated application template and build system for ember applications running on express hosted in node.

  • An Application Template
    • Using the pods
    • Supporting multiple runtime environments and local development
  • Gulp tasks for building our standard template
    • For web hosting and desktop applications
    • Use of file naming conventions to build output
    • Partial builds based on changes (when using --watch))

Then install all the dependencies using:

npm install

To build the application, simply run the default gulp task:

gulp

// OR with a watch

gulp --watch

// OR using local data

gulp --data

// OR with a watch and local data

gulp --watch --data

To run the application as a desktop application, run the following command:

gulp exe

TODO: document environment variables required NPM_AUTH_TOKEN NPM_EMAIL GITHUB_USER GITHUB_TOKEN GITHUB_OWNER GITHUB_PROJECT

In an application strucutre based on types with only two features (user and task), even this seems a bit complex to navitage. Now picture what this looks like with 10 or 20 different features.

In this case, as more and more features are added to our application, we are able to mentally focus our attention on just one feature (folder) at a time as all the code for that feature exists under one folder. Additionally, by looking at only the folder structure we can maintain a good mental model about what the application does.