npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2021 – Pkg Stats / Ryan Hefner




see numeric timestamps in text as dates





CircleCI Coverage Status semantic-release Commitizen friendly npm version

Our work involves lots of numeric timestamps in JSON. This leads to a lot of log output like:

[2020-04-01 18:32:22 TrackedEntityActivityRecordAPI] INFO calling historian.putData:  { '_org/5/Employees/148':
{ t: [ 1585777672134, 1585778400000 ],
  v: [ 'Stuffing', null ],
  beginTime: 1585777672134,

Which can be tedious to debug because numeric timestamps are inscrutable. date-goggles helps by searching for numbers that seem to be timestamps and converting them to Dates:

[2020-04-01 18:32:22 TrackedEntityActivityRecordAPI] INFO calling historian.putData:  { '_org/5/Employees/148':
{ t: [ 4/1/2020, 4:47:52 PM, 4/1/2020, 5:00:00 PM ],
  v: [ 'Stuffing', null ],
  beginTime: 4/1/2020, 4:47:52 PM,

Table of Contents

Node.js API

dateGoggles(input, options)

Transforms the output with format(parse(input, options), options). See parse and format for options documentation.

parse(input, options)

Parses input text.


input: string (required)

The input to parse.

options.unit ('milliseconds' | 'seconds', optional)

The timestamp unit. If omitted, tries to guess based upon the input or numeric options.min/options.max.

options.min (number | Date | null | undefined, optional)

Numbers found in the input less than this will not be considered timestamps. If you pass null, no lower bound is used. If undefined or omitted, defaults to 10 years ago.

options.max (number | Date | null | undefined, optional)

Numbers found in the input greater than this will not be considered timestamps. If you pass null, there's no upper bound. If undefined or omitted, defaults to 5 years into the future.

Returns: Array<string | Date>

The input split up in to substrings in which no timestamps were found, and timestamps converted to Dates.

format(ast, options)

Formats a parsed AST.


ast: Array<string | Date> (required)

The AST output of parse.

options.formatDate ((date: Date) => string, optional)

Customizes how Dates are formatted.

Returns: string

The formatted output.


The CLI is pretty basic and doesn't have any options to customize output right now, it just parses file arguments or stdin and outputs using date.toLocaleString():

date-goggles app1.log app2.log


some-command | date-goggles