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

zlook

v0.0.3

Published

File Change Watcher, Optize for multiple watcher together by sharing events

Readme

zlook

Filesystem watcher for ZeruxJS, with shared in-process subscriptions, native notifications and a polling fallback. File updates are reported once after debouncing, and watchers are disposed when the last subscriber unsubscribes.

import { startWatcher } from 'zlook';
const stop = startWatcher('src', (event) => console.log(event.file, event.type), {
  debounceMs: 75,
  pollIntervalMs: 1500,
  ignored: (file) => file.endsWith('.log'),
  onError: console.error
});
// During shutdown: stop();

Events: new, update, delete; paths are relative to the watched root. Default exclusions: .git, node_modules. Symbolic links are not traversed. scan and diff are exported for custom watcher integrations.

Limitations: sharing is process-local, not cross-process; polling uses file metadata, so a same-size write preserving modification time may be missed; a complete scan costs O(files). Filesystem read errors are surfaced through onError. Watch paths should be trusted; callbacks execute in the caller's process.

Shared watcher lifecycle

Use watchDirectory() when you need to await the baseline scan or force reconciliation:

import { watchDirectory } from 'zlook';
const watcher = watchDirectory('./src', (event) => console.log(event), {
  ignored: file => file === '.cache' || file.startsWith('.cache/'),
  pollIntervalMs: 2000,
  onError: console.error
});
await watcher.ready;
await watcher.flush();
watcher.close();

Subscribers to the same directory share underlying watchers without sharing their ignore rules. startWatcher() is retained for existing callers and returns a disposal callback. The scanner does not traverse symlinks.

Section 79 watcher validation

watchDirectory(root, callback, { debounceMs, pollIntervalMs, onError }) validates callback/root types and integer millisecond settings before creating any shared native watcher. Polling must be at least 100ms when configured; intervals are bounded to ten minutes. Subscriber callbacks remain isolated, errors are reported through onError, and handles must be closed during hot reload/unmount. Filesystem symlinks are never traversed by the recursive scan. The fallback polling path is retained for hosts where recursive fs.watch is unsupported. Test with node --test test/*.test.mjs after building.

Release 0.0.2

Prepared to validate npm trusted publishing through GitHub Actions.

Release 0.0.3

Synchronized ecosystem release, including Zuixs CSS-entry support and documentation updates. Existing placeholder packages retain their documented limitations.