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 🙏

© 2026 – Pkg Stats / Ryan Hefner

count-pieces

v0.1.0

Published

Gives you an inventory of tokens needed to write a given program

Downloads

17

Readme

pieces

Count how many pieces (tokens) you need to build a given program.

Install

$ npm install count-pieces

Command line usage

$ pieces path/to/file.c
{
 "area-comment": 168,
 "area-comment continue": 0,
 "line-comment": 0,
 "string": 71,
 "char": 45,
 "char-continue": 0,
 "directive": 32,
 "open-paren": 409,
 "close-paren": 409,
 "open-square": 123,
 "close-square": 123,
 "open-curly": 162,
 "close-curly": 162,
 "operator": 2264,
 "identifier": 2592,
 "number": 326,
 "whitespace": 2980,
 "line-continue": 5
}

# Or, e.g. force tokenization as javascript
$ pieces path/to/unknown_language js
... output ...

Library usage

var pieces = require("count-pieces");
var fs = require("fs");

var filename = "path/to/file.c";
var source_code = fs.readFileSync(filename, "utf-8");

var inv = pieces.inventory(source_code, filename);
# Or, to force the language to be C:
var inv = pieces.inventory(source_code, "c");

TODO

  • Tweak regexes, figure out what the continues are and if we need them
  • Count newlines, spaces, and tabs (which could be spaces) individually
  • Count operators and keywords individually
  • Pair up opening and closing tokens, like parens
  • More languages
  • Allow multiple input files, maybe directories