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

@hardlydifficult/collections

v1.0.18

Published

Opinionated collection helpers for the patterns we actually use: batching work and walking paths bottom-up.

Readme

@hardlydifficult/collections

Opinionated collection helpers for the patterns we actually use: batching work and walking paths bottom-up.

Installation

npm install @hardlydifficult/collections

Quick Start

import { inBatches, bottomUp } from "@hardlydifficult/collections";

for (const batch of inBatches([1, 2, 3, 4, 5, 6, 7], 3)) {
  console.log(batch);
}
// [1, 2, 3]
// [4, 5, 6]
// [7]

for (const dirsAtDepth of bottomUp([
  "src/components/Button",
  "src/components",
  "src",
])) {
  console.log(dirsAtDepth);
}
// ["src/components/Button"]
// ["src/components"]
// ["src"]

Work Batching

inBatches

Split a readonly array into sequential batches.

function inBatches<T>(items: readonly T[], size: number): T[][]

Use this when the caller is processing work, not thinking in terms of array chunking.

import { inBatches } from "@hardlydifficult/collections";

for (const batch of inBatches(files, 5)) {
  await Promise.all(batch.map(processFile));
}

Bottom-Up Path Processing

bottomUp

Group paths deepest-first for bottom-up processing.

function bottomUp(paths: readonly string[]): string[][]

Depth is computed from normalized slash-separated segments, so repeated or trailing slashes do not change grouping depth.

import { bottomUp } from "@hardlydifficult/collections";

for (const dirsAtDepth of bottomUp(["a/b/c", "a/b", "a", "x/y"])) {
  console.log(dirsAtDepth);
}
// ["a/b/c"]
// ["a/b", "x/y"]
// ["a"]

Compatibility Exports

The lower-level names are still available when they read better in a given call site:

  • chunk(items, size) is the same behavior as inBatches(items, size).
  • groupByDepth(paths) returns { depth, paths }[] when you need the numeric depth.