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

@avolgha/changelog

v1.0.0

Published

<p><h2 align="center">changelog</h2></p>

Readme

usage

import { Changelog } from "@avolgha/changelog";

const changelog = new Changelog(".changelog.json");

changelog.entry({
    author: "avolgha",
    description: "initial commit",
    timestamp: 1690386289081,
    commitId: "b959d70",
});

changelog.save();

methods

Changelog.constructor
constructor(
   filepath: string,
   initialVersion?: string
);

Create the changelog from the stored object in the given filepath.
If there is nothing stored in the changelog, there will be a version tag created automatically. This will be the given initial version or 1.0.0 if nothing was provided.

Changelog.pushVersion()
function pushVersion(
    type: "major" | "minor" | "patch",
    identifier?: string
): void;

Set a new changelog version recording to the semver version specs.
You may find a more detailed description of the function in the source code here.

Changelog.getEntries(version?)
function getEntries(
    version?: string
): ChangelogEntry[];

Get all entries for a given version. If the version is not specified, we default back to the current stored version.

Changelog.getVersions()
function getVersions(
    type: "major" | "minor" | "patch",
    identifier?: string
): string[];

Get all stored versions from the changelog.

Changelog.entry(entry)
function entry(
    entry: ChangelogEntry
): void;

Save a new entry to the current selected version in the changelog.

Changelog.save()
function save(): void;

Store the current changelog object to the filepath given in the constructor.

formatToString(changelog)
function formatToString(
    changelog: Changelog
): string;

Save all entries of the changelog in a string.