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

apollo-datasource-firestore

v6.2.0

Published

An Apollo DataSource for Firestore

Downloads

1,625

Readme

Apollo DataSource for Firestore

JavaScript Style Guide QA Publish to NPM and GCR codecov

This is a Firestore DataSource for Apollo GraphQL Servers. It was adapted from the CosmosDB DataSource

Warning
Version 6.x and up supports apollo server v4, and, through the nature of apollo server v4 it works well with other graphql servers or even standalone.
If you need apollo server v3 support, use version 5.x of this package.

Usage

Use by creating a new class extending the FirestoreDataSource, with the desired document type. Use separate DataSources for each data type, and preferably different collections in Firestore too. Initialise the class by passing a collection reference created by the Firestore library.

export interface UserDoc {
  // a string id value is required for entities using this library.
  // It will be used for the firestore document ID but not stored in the document in firestore.
  readonly id: string
  readonly collection: 'users'
  // the createdAt and updatedAt timestamps stored by firestore natively are
  // available as properties as well
  readonly createdAt: Timestamp
  readonly updatedAt: Timestamp
  name: string
  groupId: number
}

export interface PostsDoc {
  readonly id: string
  readonly collection: 'posts'
  // the createdAt and updatedAt timestamps stored by firestore natively are
  // available as properties as well
  readonly createdAt: Timestamp
  readonly updatedAt: Timestamp
  title: string
}

export class UserDataSource extends FirestoreDataStore<UserDoc> {}
export class PostsDataSource extends FirestoreDataStore<PostsDoc> {}

const usersCollection: CollectionReference<UserDoc> = firestore.collection('users')
const postsCollection: CollectionReference<PostsDoc> = firestore.collection('posts')

const server = new ApolloServer({
  typeDefs,
  resolvers
})

const { url } = await startStandaloneServer(server, {
  async context () {
    const { cache } = server
    return {
      // We create new instances of our data sources with each request.
      // We can optionally pass in our server's cache, or logger
      dataSources: {
        users: new UserDataSource(usersCollection, { cache }),
        posts: new PostsDataSource(postsCollection, { cache })
      }
    }
  }
})

Custom queries

FirestoreDataSource has a findByQuery method that accepts a function taking the collection as its only argument, which you can then create a query based on. Can be used in resolvers or to create wrappers.

Example of derived class with custom query methods:

export class UserDataSource extends FirestoreDataStore<UserDoc> {
  async findManyByGroupId (groupId: number) {
    return this.findManyByQuery(c => c.where('groupId', '==', groupId).limit(2))
  }

  async findOneByEmail (email: string) {
    return this.findManyByQuery(c => c.where('email', '==', email).limit(1))?.[0] ?? undefined
  }
}

Write Operations

This DataSource has some built-in mutations that can be used to create, update and delete documents.

await context.dataSources.users.createOne(userDoc)

await context.dataSources.users.updateOne(userDoc)

await context.dataSources.users.updateOnePartial(userId, { name: 'Bob' })

await context.dataSources.users.deleteOne(userId)

Batching

Batching is provided on all id-based queries by DataLoader.

Caching

Caching is available on an opt-in basis by passing a ttl option on queries.