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

captain-log

v0.2.0

Published

The log from your favorite captains

Downloads

10

Readme

captain-log

Automating the logs from your favorite captains

Very WORK IN PROGRESS

Install

npm install captain-log

Usage

const captain = require('captain-log')
captain([{
  title: 'What happened (ongoing)', // This will be the title of this group of issues
  repo: 'ipld/specs', // this is the repo to get these from
  state: 'open', // want open issues or closed ones?
  labels: [], // any label to filter?
  exclude_labels: ['needs spec'], // any label to exclude?
  todo: true, // want to show the list as a todo?
  since: '2016-09-10T12:00:00Z', // want to get them from a particular time?
  exclude: [13], // want to exclude a particular issue?
  prefix: ':tada:' // wants to prefix each issues with a special emoji 🎉?
}] [, optionallyYourBasicAuth])

will output

### What happened (ongoing)
- :tada: [ ] #19 : Idea for permanent mutable links
- :tada: [ ] #14 : Adding Introduction, Abstract and Scope
- :tada: [ ] #12 : Skeleton of IPLD v1 spec
- :tada: [ ] #4 : Selectors: Use cases (from Q3 Workshop)

See a better demo for ipld/specs (code here)

Quick history

I learned the practice of writing a captain.log from @daviddias in his work on js-ipfs (see his really cool log). When I started my captain.log I found really useful to list all the different issues that are open, closed, that need a spec that had something happening & so on. This process is very slow for humans but fast for machines :)

License

MIT