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

gatsby-plugin-opensearch

v1.4.0

Published

Gatsby plugin that automatically creates a OpenSearch description file for your website

Readme

gatsby-plugin-opensearch

Create an OpenSearch description for your Gatsby site.

NOTE: This plugin only generates output when run in production mode! To test your OpenSearch description, run: gatsby build && gatsby serve

Install

npm install gatsby-plugin-opensearch

How to Use

// In your gatsby-config.js
siteMetadata: {
  siteUrl: `https://www.example.com`,
},
plugins: [{
  resolve: `gatsby-plugin-opensearch`,
  options: {
    shortName: 'Github',
    description: 'Search Github',
    searchTemplate: '/search?q={searchTerms}',
    searchForm: '/search',
  },
}]

Above is the minimal configuration required to get started. The generated OpenSearch description will be included on all of your site's pages.

For more information about OpenSearch can be found here.

Options

The defaultOptions here can be overridden.

The options are as follows:

  • output (string) The filepath and name. Defaults to /opensearch.xml.
  • shortName (string) A short name for the search engine. It must be 16 or fewer characters of plain text, with no HTML or other markup.
  • description (string) A brief description of the search engine. It must be 1024 or fewer characters of plain text, with no HTML or other markup.
  • searchTemplate (string) The pathname along with any required query parameters. Parameters to be populated should be wrapped in curly brackets (e.g. {searchTerms}). More details of available parameters can be found here. This string will be appended to the siteUrl to generate the OpenSearch description file. Any characters which are invalid in XML must be escaped (e.g. & -> &)
  • searchForm (string) The pathname for the site's search page. This allows Firefox users to visit the site directly.
  • createLinkInHead (boolean) Whether to populate the <head> of your site with a link to the OpenSearch description file. Defaults to true.
  • image (object) Allows configuration of an icon for the search engine (optional).
  • image.width (number) The width of the icon
  • image.height (number) The height of the icon
  • image.src (string) The pathname for the icon, e.g. /favicon.ico. The site URL will be prefixed to the start