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

@martinreiche/gatsby-firestore

v1.0.2

Published

Gatsby source plugin for connecting Firestore as data source (including subcollections)

Readme

gatsby-firestore npm node

Gatsby plugin for connecting Firebase Firestore as a data source. Supports subcollections.

Usage

  1. Generate and download a Firebase Admin SDK private key by accessing the Firebase Project Console > Settings > Service Accounts

  2. Rename and put the downloaded .json crendtial file somewhere in the GatsbyJS project (e.g. ./credentials.json)

  3. Add gatsby-source-firestore as a dependency by running using npm or yarn:

    npm i @martinreiche/gatsby-firestore
    # or
    yarn add @martinreiche/gatsby-firestore
  4. Configure settings at gatsby-config.js, for example:

    module.exports = {
      plugins: [
        {
          resolve: `@martinreiche/gatsby-firestore`,
          options: {
            // credential or appConfig
            credential: require(`./credentials.json`),
            appConfig: {
              apiKey: 'api-key',
              authDomain: 'project-id.firebaseapp.com',
              databaseURL: 'https://project-id.firebaseio.com',
              projectId: 'project-id',
              storageBucket: 'project-id.appspot.com',
              messagingSenderId: 'sender-id',
              appID: 'app-id',
            },
            types: [
              {
                type: `Book`,
                collection: `books`,
                map: doc => ({
                  title: doc.title,
                  isbn: doc.isbn,
                  author___NODE: doc.author.id,
                }),
              },
              {
                type: `Author`,
                collection: `authors`,
                map: doc => ({
                  name: doc.name,
                  country: doc.country,
                  books___NODE: doc.books.map(book => book.id),
                }),
              },
            ],
          },
        },
      ],
    };

    Note that you will need to have books and authors in Firestore matching this schema before Gatsby can query correctly, e.g books__NODE on author needs to be an array with books as a key of reference types to book documents.

    Test GraphQL query:

    {
      allBooks {
        edges {
          node {
            title
            isbn
            author {
              name
            }
          }
        }
      }
    }

Support for subcollections

To query subcollections, you have to specify the subCollection Array in the types configuration. They can be nested infinitely deep as long as they exist in Firestore. For example, if books were a subcollection of authors in Firestore, you could do the following:

module.exports = {
  plugins: [
    {
      resolve: `@martinreiche/gatsby-firestore`,
      options: {
        // credential or appConfig
        credential: require(`./credentials.json`),
        appConfig: {
          apiKey: 'api-key',
          authDomain: 'project-id.firebaseapp.com',
          databaseURL: 'https://project-id.firebaseio.com',
          projectId: 'project-id',
          storageBucket: 'project-id.appspot.com',
          messagingSenderId: 'sender-id',
          appID: 'app-id',
        },
        types: [
          {
            type: `Author`,
            collection: `authors`,
            map: doc => ({
              name: doc.name,
              country: doc.country,
            }),
            subCollections: [
              {
                type: `Book`,
                collection: `books`,
                map: doc => ({
                  title: doc.title,
                  isbn: doc.isbn,
                }),
              },
            ],
          },
        ],
      },
    },
  ],
};

books now become children of author and you can query them like this:

{
  allAuthor {
    edges {
      node {
        name
        childrenBook {
          title
          isbn
        }
      }
    }
  }
}

Configurations

| Key | Description | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | credential | Credential configurations from downloaded private key | | types | Array of types, which require the following keys (type, collection, map) | | types.type | The type of the collection, which will be used in GraphQL queries, e.g. when type = Book, the GraphQL types are named book and allBook | | types.collection | The name of the collections in Firestore. Supports nested collections like authors/<authorId>/books where <authorId> is the ID of one specific author record | | types.map | A function to map your data in Firestore to Gatsby nodes | | types.subCollections | Optional: Array of types for the current type --see types |

Acknowledgement