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

@lsdsoftware/utils

v2.1.1

Published

Useful JavaScript utilities

Readme

Useful JavaScript utilities

Line Reader

Split text into lines

import { makeLineReader } from "@lsdsoftware/utils"

myStream.pipe(makeLineReader(line => console.log(line)))

Semaphore

Control concurrent access to resources

import { makeSemaphore } from "@lsdsoftware/utils"

const semaphore = makeSemaphore(3)

const result = await semaphore.runTask(async () => {
  //use the limited resource
})

Connect Socket

Observable wrapper for net.connect (see connect-socket.test.ts for usage)

Worker Rotator

Rotate worker instances over a request stream.

import { makeWorkerRotator } from "@lsdsoftware/utils"

const subscription = makeWorkerRotator({
  makeWorker,
  workerTtlMs: 60_000,
  request$,
  maxPendingRequests: 100,
  onEvent: event => console.debug('[worker-rotator]', event)
}).subscribe()

Contract:

  • The returned observable is cold and does not emit values. Each subscription creates its own rotator engine and subscribes to request$; share the returned observable if you want one engine with multiple observers.
  • onEvent receives optional lifecycle events for logging, tracing, or diagnostics.
  • Requests emitted before the first worker is ready, or between workers, are buffered and handed to the next worker.
  • maxPendingRequests caps the no-worker buffer and errors the rotator when exceeded. The default is Infinity.
  • Pending requests are considered handed off once they are passed to worker.process. Delivery retries, acknowledgements, and exactly-once guarantees belong in the worker or an upstream queue.
  • Completing request$ means no more input, but it does not define the rotator lifecycle. The engine runs until the returned observable is unsubscribed or errors.
  • worker.relieve() is called during worker teardown. Implementations should make it safe to call more than once.

CLI Worker Rotator

Rotate child processes that communicate over stdin/stdout using a line-oriented request/response protocol, such as JSONL.

import { spawn } from "node:child_process"
import { makeCLIWorkerRotator } from "@lsdsoftware/utils"

const subscription = makeCLIWorkerRotator({
  spawnWorkerProcess: () => spawn("my-jsonl-worker", {
    stdio: ["pipe", "pipe", "inherit"]
  }),
  workerTtlMs: 60_000,
  request$,
  maxPendingRequests: 100,
  onEvent: event => console.debug('[cli-worker-rotator]', event)
}).subscribe()

Each request writes exactly one stdin line. Each stdout line is paired with the next pending request in order. Child processes should write logs to stderr.

For custom framing or multiplexed protocols, implement Worker<R> directly and use makeWorkerRotator.

If a worker exits before producing a matching stdout line for a written request, that request's output$ is not resolved by this adapter. Apply timeout or cancellation around each request if the caller needs bounded waits.