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

@retrogen/core

v0.0.2

Published

generates data from an organization you pass in

Downloads

89

Readme

@retrogen/core

The core functionality of retrogen, a tool for generating retrospectives for GitHub activity.

Prerequisites

To run this project, it's assumed that you have a GitHub Personal Access Token configured in your environment under the GITHUB_TOKEN environment variable. You can either do this manually, automatically with your own tooling, or by adding an appropriately configured .env file to your project.

Usage

Basic usage:

// source: ./examples/default.js

const core = require('@retrogen/core')

async function generate () {
  const dates = {
    start: '2022-01-01',
    end: '2022-01-31'
  }

  const data = await core('nodejs', dates)

  console.log(JSON.stringify(data, null, 2))
}

generate()

Addtional examples can be found in ./examples/.

API

Assuming you've required this module as core:

  • core(owner, dates, options)
    • owner String (required): The GitHub name of the owner of the repository. This can be a user or an organization.
    • dates Object (required):
      • start String (required): The start date of the query we'll send to GitHub. Should be formatted as YYYY-MM-DD.
        • Example: '2022-01-01'
      • end String (required): The end date of the query we'll send to GitHub.Should be formatted as YYYY-MM-DD.
        • Example: '2022-01-31'
    • options Object (optional):
      • sort String (optional): The sort order of the query we'll send to GitHub. You can find the valid options on GitHub's Docs.
        • Examples: stars, interactions, updated
        • Default: 'updated'
      • per_page Number (optional): The number of results to return per page.
        • Default: 100

The goal with these API docs is to have a consistent style of documentation for each module in the monorepo. If there's inconsistencies, please feel free to open an issue to let the maintainers know