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

clogx

v1.2.0

Published

A simple CLI tool to generate a per repo commit log of all directories in the current working directory for submission as proof of work completed. Handy if you are a freelancer who needs to provide documentation to clients.

Downloads

8

Readme

ClogX

A pretty log of your montly commits output to a docx file. Handy for reporting your monthly progress to your manager or team.

Install

npm install clogx

Usage

Requirred Arguments

  1. --month - The month you want to generate the log for. This can either be the full month name, or the first 3 letters of the month name.
  2. --author - The author of the commits you want to generate the log for. Use either the name listed in the commit, or the email address.

Optional Arguments

  1. --pdf - If you want to generate a pdf file instead of a docx file. This requires that you have libreoffice installed on your system.
  2. --fetch - Makes sure to fetch all the commits from the remote repository before generating the log. This is useful if you have not pulled the latest commits from the remote repository.
  3. --waka - Includes editing time for the month for each repo from wakatime. This requires that you have a wakatime account with a wakatime api key. If you are using wakatime in your editor the api key will already be stored in ~/.wakatime.cfg. If not, you will be prompted for the key and it will be stored in ~/.wakatime.cfg to be available to your editor. If you aren't using wakatime in your editor though, it doesn't make much sense to include these statistics in the generated commit log.

Examples

Running local installation

clogx --month=May --author="John Doe" --pdf --fetch --waka

Running with npx

npx clogx --month=May --author="John Doe" --pdf --fetch --waka