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

gatsby-plugin-aws-elasticsearch

v0.2.1

Published

A plugin for Gatsby to synchronise content between Gatsby and AWS Elasticsearch

Downloads

13

Readme

gatsby-plugin-aws-elasticsearch

Version License

An experimental plugin for Gatsby to synchronise content between Gatsby and AWS Elasticsearch. You can write a GraphQL query to fetch the data, and parse it to a format which will be used for Elasticsearch.

Requirements

  • Node.js v10 or newer.
  • An AWS Elasticsearch instance, and API credentials for it.

Installation

First, install the package using npm or yarn.

yarn add -D gatsby-plugin-aws-elasticsearch

or

npm install --save-dev gatsby-plugin-aws-elasticsearch

Getting started

To use the plugin, add it to your gatsby-config.js:

export default {
  // ...
  plugins: [
    {
      resolve: 'gatsby-plugin-aws-elasticsearch',
      options: {
        // See below
      }
    }
  ]
}

Options

The following options are available:

  • enabled - Whether the plugin is enabled or not. Can be used to toggle the synchronisation. This defaults to false.

    {
      enabled: !!process.env.ELASTIC_SYNC
    }
  • query - A GraphQL query to fetch the data.

    {
      query: `
        query {
          allMdx {
            nodes {
              frontmatter {
                title
              }
              excerpt
            }
          }
        }
      `
    }
  • selector - A function which takes the raw GraphQL data and returns the nodes to process.

    {
      selector: (data) => data.allMdx.nodes
    }
  • toDocument - A function which takes a single node (from selector), and returns an object with the data to insert into Elasticsearch. The object must contain an id field, which is used as the ID for the document. Note that the data should be JSON serialisable.

    {
      toDocument: (node) => ({
        id: node.slug,
        title: node.frontmatter.title,
        excerpt: node.excerpt
      })
    }
  • endpoint - The HTTP endpoint of the Elasticsearch server. It should not have a trailing slash.

    {
      endpoint: process.env.ELASTIC_AWS_ENDPOINT
    }
  • index - The name of the index to insert the data into. If the index does not exist, it will be created.

    {
      index: 'articles'
    }
  • mapping - An object with the mapping info for the index. This will overwrite the current settings for the index. Please refer to the Elasticsearch docs for an overview of the options.

    {
      mapping: {
        title: {
          type: 'keyword'
        },
        excerpt: {
          type: 'text'
        }
      }
    }
  • accessKeyId - The AWS IAM access key ID.

    {
      endpoint: process.env.ELASTIC_AWS_ACCESS_KEY_ID
    }
  • secretAccessKey - The AWS IAM secret access key.

    {
      endpoint: process.env.ELASTIC_AWS_SECRET_ACCESS_KEY
    }