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

bug-me

v1.0.3

Published

get a bug to look at based on what you're interested in

Downloads

7

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

chrisdickinsonchrisdickinson

Keywords

nodebugmetriagebugs

Readme

bug-me

A package exposing the data from nodebug.me. Contains both a CLI and require-able module.

$ bug-me
usage: bug-me [<options>]

    -h, -?, --help        show this help
    -r, --reproducible    show issues with reproduction steps
    -c, --consensus       show issues that have consensus on a solution
    -d, --duplicates      show issues that have duplicates
    -w, --wrong-repo      show issues that are in the wrong repo
    -f, --is-feature      show issues that have been approved as features
                          by a core team member
    -v, --version <ver>   show issues that have been reproduced 
                          against version <ver>, with acceptable values
                          of "0.10" or "0.11"
$ bug-me -c -f
# ... all issues that have consensus or are features ...

Or from Node:

var concat = require('concat-stream');
var bugs = require('bug-me');

bugs().pipe(concat(function(bugReports) {
  bugReports.length
}))

API

bugs() → Readable Stream<BugReport>

Bugs will return an objectMode readable stream of bug report objects, suitable for piping to an objectMode writable stream.

BugReport

An object tallying the results of bug reports for a given github issue. Detailed here.

License

MIT