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

burnchart

v4.0.0-rc.1

Published

GitHub Burndown Chart as a Service. Answers the question "are my projects on track"?

Downloads

7

Readme

burnchart

GitHub Burndown Chart as a Service. Answers the question "are my projects on track"?

Features

  1. Running from the browser, apart from GitHub account sign in which uses Firebase backend.
  2. Private repos; sign in with your GitHub account.
  3. Off days; specify which days of the week to leave out from ideal burndown progression line.
  4. Trend line; to see if you can make it to the deadline at this pace.
  5. Different point counting strategies; select from 1 issues = 1 point or read size from issue label.

Quickstart

$ yarn install
$ ./cli.js --port 1234
# burnchart/4.0.0 started on port 1234

FAQ

Browser 404 Errors

If you are running a dev mode on localhost (yarn start) and start the app by navigating to a URL that contains a . character - Vite serves a 404. To fix this either navigate to the page through homepage or start the app through the cli - yarn start:preview.

GitHub Bugs

Some milestones show "incorrect" issues associated. Consider the two following views of a milestones:

  • https://github.com/nhn/tui.calendar/milestone/6 - 21 closed issues
  • https://github.com/nhn/tui.calendar/issues?q=is%3Aissue+milestone%3Av1.12.13+is%3Aclosed - 11 closed issues (what we show)

Configuration

At the moment, there is no UI exposed to change the app settings. You have to either edit the src/config.js file or use URL query string parameters to override these on a per-user basis.

An array of days when we are not working where Monday = 1. The ideal progression line won't drop on these days.

"off_days": [ ]

Choose from ONE_SIZE which means each issue is worth 1 point or LABELS where issue labels determine its size.

"points": "ONE_SIZE"

If you specify LABELS above, this is the place to set a regex used to parse a label and extract points size from it. When multiple matching size labels exist, their sum is taken.

"size_label": /^size (\d+)$/

Firebase

Signup for Firebase and go to your console and create a new project there.

You can leave the Database/Storage section as is, you only want to configure your "Authentication". There, enable "GitHub" and add your domain in "Authorised domains". Mine is set to radekstepan.com and type: Custom. If you want to run the app locally, you may want to add localhost and/or 0.0.0.0 as well.

Since you are using your own Firebase project, you want to copy a couple of keys/ids into the firebase.* section of src/config.js.

  • firebase.apiKey is "Web API key" from the "Settings" page (in "Project Overview")
  • firebase.authDomain is one of the authorised domains in "Authentication", then "Sign-in method"