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

asljs-part

v0.1.42

Published

Project artefact tracing framework and CLI for markdown-defined project artefacts.

Readme

part

Part of Alexandrite Software Library - a set of high-quality, performant JavaScript libraries for everyday use.

Markdown-defined project artefact tracing framework with a CLI for inventory, definition inspection, and rule checks.

Quick Start

Create a definition such as Todo Item.md:

# Todo Item

A task that needs to be done.

## Properties

- Due date: when it needs to be done.

## Location

- Files: ../Todo Items/*.md

## Rules

- R1 - Due date must be in the future.

Crate a data providing function in parts/Todo Item.js:

export async function getData(artefact, context)
{
  const text =
    await context
      .markdownDocuments
      .read(
        artefact.path);

  const dueDate =
    text.match(/- Due date: (.*)/)[1];

  return { dueDate };
}

Create a matching rule in parts/Todo Item_R1.js:

export async function validate(artefact, context)
{
  const artefactData =
    await context.artefactData.tryGetArtefactData(artefact);

  const dueDate =
    artefactData['Todo Item'].dueDate;

  const now = new Date();

  if (dueDate <= now) {
    throw new Error('Due date must be in the future.');
  }
}

Create an artefact in Todo Items/Buy milk.md:

# Buy milk

- Due date: 2026-07-01

Buy milk on the way home.

Run inventory:

part inventory

Bootstrap a definitions folder:

part init --definitions artefacts

Example output:

| File                   | Definitions |
| ---------------------- | ----------- |
| Todo Items/Buy milk.md | Todo Item   |

If you want to embed PART in your own tooling instead of shelling out, import the package-root helpers from asljs-part and call the report builders or runCli(...) directly.