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

@bitstillery/wakamonth

v2.0.1

Published

Generate working hour reports from Wakatime/Wakapi data

Downloads

2

Readme

Wakamonth

Generate reports of working time in hours per Git branch, based on your Wakatime/Wakapi activity. Please notice that time tracked by these tools are an estimate; not legally binding, so make sure to always verify the output of Wakamonth manually when using it for billing reports / invoices.

Getting started

A wakatime.cfg file is required with api_key and api_url set. Use like:

npx @bitstillery/wakamonth -y 2024 -m 1 -p myproject report
# Export to Excel sheet:
npx @bitstillery/wakamonth -y 2024 -m 1 -p myproject report -e xlsx
# Target specific user:
npx @bitstillery/wakamonth -y 2024 -m 1 -p myproject -u myuser report -e xlsx

Config

A Wakamonth config file is not required, unless you want to change its defaults:

{
    "autolink": {
        "enabled": "false",
        "issue_regex": "^\\d+",
        "url": "https://codeberg.org/organisation/{{project}}/issues/{{issue}}"
    },
    "include": {
        "ignore_regex": "^-fix-|main|staging"
    },
    "precision": 30,
    "spread_unallocated": true
}
  • autolink: automatically links a branch name to an issue in the export
  • include.ignore_regex: regex for branch names to exclude from the total count
  • precision: 60 (hours) | 30 (half-hourly) | 15 (quarter-hourly)
  • spread_unallocated: Unallocated hours will be spread across other branches if active
wget https://raw.githubusercontent.com/bitstillery/wakamonth/main/.wakamonthrc.example -o ~/.wakamonthrc
vim ~/.wakamonthrc

Development

git clone https://github.com/bitstillery/wakamonth.git
cd wakamonth
pnpm i
./wakamonth.js -y 2024 -m 1 -p myproject report -e stdout