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

@zbsearch/searchbox-core

v4.0.0

Published

Framework-neutral primitives behind the ZBSearch search boxes

Readme

@zbsearch/searchbox-core

The framework-neutral half of the ZBSearch search boxes: the types they agree on, the text and result helpers they share, and the stylesheet they both render.

@zbsearch/searchbox-react and @zbsearch/searchbox-vue are thin layers over this package, which is why the two behave identically. Depend on it directly when you are building a search UI for another framework, or none at all.

It has no framework dependency of any kind.

Installation

npm install @zbsearch/searchbox-core

Types

interface SearchHit {
  id: string
  url: string
  title: string
  section?: string
  snippet?: string
  breadcrumb?: string[]
  category?: string
}

type Searcher = (term: string, signal: AbortSignal) => Promise<SearchHit[]> | SearchHit[]

Helpers

import { groupHits, highlight, snippetAround, wrapIndex } from '@zbsearch/searchbox-core'

groupHits(hits) // buckets hits by page, preserving relevance order
highlight(text, query) // alternating matched/unmatched segments
snippetAround(text, query, 160) // an excerpt centred on the first match
wrapIndex(current, +1, length) // arrow-key movement that wraps at both ends

highlight returns segments rather than HTML, so a framework can render matches without dangerouslySetInnerHTML or v-html. It is built on @zbsearch/highlight.

Recent searches

import { addRecentSearch, readRecentSearches, removeRecentSearch } from '@zbsearch/searchbox-core'

All three take a storage object, so they work with localStorage, sessionStorage, or a stub in tests. A corrupt or unavailable store degrades to an empty list rather than throwing.

Labels

defaultLabels holds the English copy; resolveLabels(overrides) merges a partial set over it.

Stylesheet

import '@zbsearch/searchbox-core/styles.css'

Every value is a --zbs-* custom property. Light is the default, dark follows the OS colour scheme, and an explicit data-theme attribute on any ancestor wins over both.

The three cases are kept mutually exclusive rather than layered by source order, because CSS minifiers merge rules that share declarations and move them to the position of the first — which silently reorders a cascade that only order kept correct.

License

Apache-2.0