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

search-client

v2.2.0

Published

Javascript library for executing searches in the Haive search-index via the SearchManager REST interface.

Readme

Haive SearchClient

NPM NPM Downloads Build Status

Project links

  • Documentation
  • Node Package Manager
  • CDN at JSDelivr
  • GitHub repository
  • Issues
  • Changelog

About

The SearchClient library makes it easy to hook up your search-UI to a Haive SearchManager instance (see the app-search features of Haive App Search here).

Note: in v2+ the package namespace is Haive (instead of IntelliSearch)

The package handles all the backend web-services so that you can focus on the user interface instead.

The SearchClient wraps and manages all the Haive SearchManager REST web-services:

  • Autocomplete - Lookups query-text and suggests words to help write the query.
  • Find - Searches the index based on the current query (query-text, filters, ...).
  • Categorize - Generates a category tree with counts based on the current query (query-text, filters, ...)

In addition, it also handles a OpenID authentication.

Use in NPM projects

For projects that consumes npm packages natively you add this package as you would add any other npm-package:

> npm install --save search-client

Since we have implemented the search-client in Typescript all the data-types and signatures are available for your IDE to use as intellisense. Please also use the documentation available in the generated API-documentation in the search-client doc-folder (typically ./node_modules/search-client/doc/index.html).

Use in browser (via script-tag)

For web-pages that needs to have a script-tag embedded you can fetch the file(s) needed via the jsDelivr cdn, like this:

<script src="//cdn.jsdelivr.net/npm/search-client@{version}/dist/Haive.min.js"></script>

- where {version} is to be replaced with the actual version you want.

CDN version aliases:

We strongly recommend that you use the full version id for production sites. For development sites we do recommend the same, but we also see that using a version alias might be handy in some cases.

  • latest You can use the jsdelivr version alias latest to always just get the latest version. Just be warned that your site is at high risk of breaking when new versions of the search-client are released. If the search-client library is updated and somehow is no longer compatible with your code, then your site will potentially break and stop working.

  • <Major> (i.e. 1) This means that it will get the latest version for the given major version. Note that the same warning as for latest applies, although this is less risky than just getting any latest version.

  • <Major.Minor> (i.e. 1.1) This means that it will get the latest version for the given major.minor version. Note that the same warning as for latest applies, although this is less risky than both of the above options.

Note: You can replace dist with es to get different builds of the library too. For browser script you should use dist as that version is in UMD format. A benefit to using the npm system is the inclusion of map-files. These are available for the es and lib versions only. Next to the browser-bundles in the project you can find accompanying .map files that browsers are able to utilize in order to give a better debugging experience.

License

LICENCE