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

@rolldown/notify

v0.2.0

Published

Native file watching for Node.js, powered by rolldown-notify

Readme

@rolldown/notify

Node bindings for rolldown-notify with a callback API:

import { watch } from '@rolldown/notify'

const watcher = watch(
  ['/project', '/shared/vite.config.js'],
  (event) => console.log(event.kind, event.path),
  {
    ignored: ['**/node_modules/**', '**/*.map', '!**/keep.map'],
  },
)

watcher.add('/another/root')
watcher.remove('/project')
watcher.close()

Chokidar-like API

The separate @rolldown/notify/chokidar entry point adapts the callback API to Chokidar's EventEmitter interface:

import chokidar from '@rolldown/notify/chokidar'

const watcher = chokidar.watch('/project')
watcher.on('change', (path) => console.log(path))
await watcher.close()

Watch paths support Chokidar v3-style globs.

Existing files do not emit initial events, and a directory event does not synthesize events for its descendants. Removed paths whose type is unavailable from the backend emit unlink.

Use isWatched(path) to check configured watch coverage. A file root covers that file, and a directory root covers its descendants, including paths that do not exist yet. Ignored or unwatched paths return false, as does any query on a closed watcher. The check does not enumerate directories or guarantee OS event delivery. getWatched() is not supported.

unwatch() can exclude a descendant of a recursively watched root even when that descendant was not added separately. The parent remains watched by the native backend, but the adapter suppresses events below the excluded path. Adding the descendant again clears the exclusion. Adding a deeper path also clears the ancestor exclusion for the whole subtree; re-inclusion holes are not represented independently.

followSymlinks: false

Symlink behavior follows the backend: the macOS FSEvents backend canonicalizes watch roots and does not support the follow_symlinks option. Polling uses WalkDir, which follows a symlink supplied as the root independently of its follow_links setting.