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

@nebula-lab/hooks

v1.0.0

Published

React hooks with no dependency on @nebula-lab/primitives or higher layers — state/DOM/lifecycle utilities every other package can build on.

Readme

@nebula-lab/hooks

React hooks with no dependency on @nebula-lab/primitives or any higher layer — state, DOM, and lifecycle utilities every other package can build on.

Installation

npm install @nebula-lab/hooks
# or
yarn add @nebula-lab/hooks
# or
pnpm add @nebula-lab/hooks
# or
bun add @nebula-lab/hooks

Peer dependency: react ^19.0.0. Works with any of the above package managers — pick whichever your project already uses.

Module format: ESM only (no CommonJS build). Works out of the box with any bundler (Vite, Next.js, Webpack 5+, esbuild, Parcel) or native Node.js ESM. A plain CommonJS require('@nebula-lab/hooks') is not supported and throws ERR_REQUIRE_ESM — use import (or dynamic import() from a CJS file) instead.

TypeScript / JavaScript: Ships hand-written .d.ts types alongside the JS output, but nothing requires TypeScript — plain JavaScript works identically. TypeScript users get full autocomplete/type-checking for free; JavaScript users just don't see the type annotations.

What's here

  • useControllableState — the controlled/uncontrolled state pattern used by every stateful primitive (Checkbox, Select, Tabs, Switch, ...).
  • useClickOutside, useMediaQuery, useScrollLock, useFocusTrap — overlay/responsive building blocks.
  • useResizeObserver, useIntersectionObserver, useMutationObserver — DOM observation.
  • useLocalStorage, useDebounce, useId — state/value utilities.
  • useBoolean, useToggle, useStableCallback, useEventListener, usePrevious, useMounted — small general-purpose hooks.
  • useVirtualizer — windowed rendering for long lists/grids, backs @nebula-lab/react-ui's VirtualList.
  • useSwipe — pointer-based swipe gesture detection (direction + delta), backs Carousel's and SwipeableCards' drag interactions.

Import

import { useControllableState, useBoolean } from '@nebula-lab/hooks';
// or per-hook subpath
import { useControllableState } from '@nebula-lab/hooks/use-controllable-state';

Note on @nebula-lab/utilities

This package intentionally does not import from @nebula-lab/utilities (see component-library-architecture.md §2: both packages sit at the bottom of the dependency graph with no cross-dependency). Where a hook needs logic that overlaps with a utility (e.g. useFocusTrap's focusable-element query vs. isFocusable), it's duplicated locally with a comment pointing at the utilities equivalent rather than creating a cross-import.

Contributing

See the monorepo's CONTRIBUTING.md.

License

MIT