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

jovo-db-firestore

v3.6.1

Published

> To view this page on the Jovo website, visit https://v3.jovo.tech/marketplace/jovo-db-firestore

Downloads

88

Readme

Google Firestore Database Integration

To view this page on the Jovo website, visit https://v3.jovo.tech/marketplace/jovo-db-firestore

Learn how to store user specific data of your Alexa Skills and Google Actions to Google Cloud Firestore.

Tutorial: Deploy to Google Cloud

Introduction

The Firestore integration allows you to store user session data in the NoSQL service running on Google Firebase. This integration is especially convenient if you're running your voice app on Google Cloud Functions. You can find the official documentation about Firestore here: firebase.google.com/docs/firestore.

Learn more about hosting your application on Google Cloud Functions.

Configuration

Download the package like this:

$ npm install --save jovo-db-firestore

Firestore can be enabled in the src/app.js file like this:

// @language=javascript

// src/app.js

const { Firestore } = require('jovo-db-firestore');

// Enable DB after app initialization
app.use(new Firestore());

// @language=typescript

// src/app.ts

import { Firestore } from 'jovo-db-firestore';

// Enable DB after app initialization
app.use(new Firestore());

If you are using Firestore in other parts of your application and already have an intialized instance, you can just pass that into the constructor as well. This is especially helpful when using Firebase Cloud Functions. When deploying your code to Firebase Cloud Functions you don't need to provide the databaseURL and credential in the config.js file and you won't have the error related to the initializeApp method being called twice on the firebase-admin instance.

// @language=javascript

// src/app.js

const { Firestore } = require('jovo-db-firestore');

// Firebase admin and firestore initialization code
const admin = require('firebase-admin');
admin.initializeApp();
let db = admin.firestore();

// Enable DB after app initialization
app.use(new Firestore({}, db));

// @language=typescript

// src/app.ts

import { Firestore } from 'jovo-db-firestore';

// Firebase admin and firestore initialization code
import * as admin from 'firebase-admin';
admin.initializeApp();
const db = admin.firestore();

// Enable DB after app initialization
app.use(new Firestore({}, db));

Inside your config.js file you have to set your credential and your databaseURL. You can also optionally set the collection name (default is UserData):

// @language=javascript

// src/config.js

module.exports = {
    
    db: {
        Firestore: {
            credential: require('<path-to-credential-json-file>'),
            databaseURL: '<databaseURL>',
            collectionName: '<collectionName>',
        },
    },

    // ...

};

// @language=typescript

// src/config.ts

const config = {
    
    db: {
        Firestore: {
            credential: require('<path-to-credential-json-file>'),
            databaseURL: '<databaseURL>',
            collectionName: '<collectionName>',
        },
    },

    // ...

};

Using Firestore outside Google Cloud

If you use plan to use the Firestore integration while hosting your project outside Google Cloud Functions (e.g. on AWS Lambda), you have to add the following post install script to your package.json:

"scripts": {
  "postinstall": "npm install grpc --target=<function-node-version> --target_arch=x64 --target_platform=linux --target_libc=glibc"
},

You need the script because the Firestore integration depends on the firebase-admin module, which depends on the grpc module. If you simply run npm install it will download the grpc binary for your node version and operating system combination, which might differ from the one Lambda expects, which is node-v48-linux-x64-glibc. The script installs the correct binary for you. Find more about that here.