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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@johanhalse/pucko-search

v0.0.7

Published

The stupidest search

Downloads

8

Readme

Pucko search

When you thought you needed something like Lunr.js but it turned out you only needed the dumbest search.

It's so tiny!

Yup. It's designed to be more or less a drop-in for your lunr.js installation unless you're doing anything clever (so hands off those Levenshtein distances and fancy-pants vectors!) but it's only 2kb minified. The only thing it contains is a really basic algorithmic stemmer which is currently in, uh, Swedish, and a naive string search. That's what I needed when I wrote this.

Installation

Install via npm, like this:

npm install --save-dev @johanhalse/pucko-search

Usage

One difference between Lunr and Pucko when instantiating is that you need a new keyword. Otherwise the functions look pretty much the same:

import Pucko from "@johanhalse/pucko-search";
let idx = new Pucko(function() {
  this.ref("url");
  this.field("header");
  this.field("body");
  this.field("summary");

  myDocuments.forEach(doc => {
    this.add(doc);
  }, this);
});

Function reference

ref(String): change reference field

field(String): make a field in your corpus searchable

search(String): perform a search for your terms

When searching, Pucko will split any string it receives on spaces only, and the search is always case insensitive. Combined with the stemmer, this means that if you search for something like "Leva farligt" you'll get results that match the substrings ["lev", "farl"]. It'll also strip diacritics in both search term and corpus. You'll get a lot more results than Lunr, for sure. If you want to search for an exact match and not split the string by spaces, prefix your search term with ^.

Another difference versus Lunr is that you'll only get an array of strings back. Since Pucko isn't doing anything suspicious like tracking advanced matching data it makes no sense to wrap all your results with { ref: "foo" }. All you'll get back is the ref string, and you'll damn well like it.