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

history-store

v0.2.2

Published

Store history reports

Readme

history-store

historys-store is a server-side module used to store different versions of report. When used with history-trend, it becomes possible to compute any trend of any report over time.

This is a very simple persistent file system storage which is not intended to support huge volume.

Installation

To use with node:

$ npm install history-store

Usage


var // creates stores root on ../history folder
    stores = require('history-store')('../history'),
    // creates a store dedicated to IssueReport
    issueReportStore = stores.report('IssueReport'),
    // here is a typical report to store and access
    report = { date: new Date('1995-12-17T03:24:00'), issues: [{ key: 'JIRA-123', status: 'New'}, { key: 'JIRA-456', status: 'In Progress'}]};

// stores report
issueReportStore.put(report, function (err) {});

// gets all reports
issueReportStore.get(function (err, reports) {});

// it is also possible (and recommended) to stream reports individually
var stream = issueReportStore.stream();

stream.on('data', function (report) {});
stream.on('end', function (err) {});

Report can be any js object containing primitive types (Number / String / Date) with any array/object nesting. Report is JSON stringified on file system.

Date identification

History store needs to know date of report. By default, date is expected to be found in report.date. However, it is possible to define specific access to date.

// date identified by report.creationdate
stores.report('MyReport', 'creationdate')

// date identified in nested object report.status.date
stores.report('MyReport', 'status.date')

// date identified with a custom function computeDate(report) { ... }
stores.report('MyReport', computeDate)

Tests

 $ npm test