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

wc-tracker

v0.0.4

Published

Track writing progress across plain text files using git diff, with customizable intervals and a CLI

Downloads

3

Readme

wc-tracker: track writing progress across text files

Overview

wc-tracker keeps a running count of words added and deleted from any file you add to its index. Intended as a tool to track writing progress in a plain text drafting workflow, the script lets you set the tracking interval (i.e. for a daily or weekly goal) and the time of day when the interval resets.

Example

> wc-tracker README.md
# Began tracking 1 file:
# /Users/me/dev/wc-tracker/README.md
> wc-tracker
# 252 words added and 86 words removed across 8 tracked files (net change 166 words)

Installation

npm i -g wc-tracker

(Recommended to use the -g option when planning to use the command line interface)

CLI

wc-tracker <path>    start tracking file(s); report progress if already tracked
wc-tracker           report total words added and removed across tracked files

Commands:
  wc-tracker clear   delete the entire tracking index

Options:
      --help         Show help                                         [boolean]
      --version      Show version number                               [boolean]
  -v, --verbose      Run with verbose logging                            [count]
  -i, --interval     Set the length, in days, of the tracking window
  -c, --clock-start  Set what time of day the tracking window starts over
                                                                        [string]

Examples:
  wc-tracker ~/Documents/**/*.md  track the number of words added and removed in
                                   any markdown file within Documents

API

import { update, track, clear } from 'wc-tracker'
update(options, runtimeOptions, callback)

Report the aggregate counts across all files that the index is tracking.

  • options -- { interval: <int>, "clock-start": <string, e.g. "04:00"> }
  • runtimeOptions -- { verbose: <int> }
  • callback -- function (error, wordsAdded, wordsRemoved, fileCount)
track (paths, options, runtimeOptions, callback)

Try to add each file in paths to the index, then report the aggregate counts across the specified files that were already tracked; also report the paths of files that are now newly tracked.

  • paths -- [<string>, ...]
  • options -- { interval: <int>, "clock-start": <string, e.g. "04:00"> }
  • runtimeOptions -- { verbose: <int> }
  • callback -- function (error, added, removed, alreadyTrackedFileCount, newlyTrackedPaths)
clear (options, callback)

Delete the entire tracking index and cache storage.

  • options -- { confirm: <boolean> }
  • callback -- function (error)