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

@kogk/gatsby-plugin-js-search

v0.11.0

Published

gatsby plugin handy for using js-search on a gatsby site

Downloads

117

Readme

@kogk/gatsby-plugin-js-search

Gatbsy plugin impelementation of js-search for creating build-time search indexes, lazy-loaded as needed.

Table of Contents

How does it work?

At build time, you query for the data you want. The data gets stored in the public folder, but not included in any bundle (similar as images).

When you actually want to perform a search, and you call the search function returned from useSearch, then the actual request starts and starts fetching the appropriate index.

This means that you don't need to worry about your large search index affecting your bundle size etc.

Features

  • Allows you to gather content from your queried nodes relatively easily
  • Exposes a simple useSearch hook to be able to query the index

Todo

  • Further work on i18n and custom stemming etc, is probably in order

Install

yarn add @kogk/gatsby-plugin-js-search

How to use

// In your gatsby-config.js
plugins: [
  {
    resolve: '@kogk/gatsby-plugin-js-search',
    options: {
      indexes: [
        {
          // the name is used when you need to fetch the data
          name: 'name of the index',

          // see index strategies of js-search
          indexStrategy: 'ExactWordIndexStrategy',

          // the plugin filters by nodeTypes, but if you need additional filtering
          // (eg. language, whitelisting etc) you can define a CB for that here
          filter: node => isYummy(node),

          // which types of nodes in gatsby should we include
          nodeTypes: ['SomePage'],

          // ID field is used as the primary identifier for an entry - often the url
          // will suffice
          idField: 'url',

          // Which fields to index
          fields: ['title', 'tags', 'text'],

          // A function that takes the Node object and converts it to any type you like
          mapper: node => ({
            url: node.url,
            title: node.data.page_title.text,
            tags: node.tags,
            text: extractTextFromRawSlices(node.dataRaw.body)
          })
        }
      ]
    }
  }
]