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-firebase-messaging

v1.1.0

Published

Gatsby plugin to help manage Firebase messaging service worker

Downloads

331

Readme

gatsby-plugin-firebase-messaging

This plugin handles the setup, configuration, and, if needed, removal of service workers required by Firebase cloud messaging. The rest of the usage of Firebase messaging will follow your particular project's needs, and can be set up as outlined in Firebase's documentation.

Install

npm i gatsby-plugin-firebase-messaging

How to use

General Setup

// Include in gatsby-config.js
plugins: [
  {
    resolve: `gatsby-plugin-firebase-messaging`,
    options: {
      //required unless removeFirebaseServiceWorker == true
      config: { 
        apiKey: 'YOUR_FIREBASE_API_KEY',
        appId: 'YOUR_FIREBASE_APP_ID',
        messagingSenderId: 'YOUR_FIREBASE_MESSAGING_SENDER_ID',
        projectId: 'YOUR_FIREBASE_PROJECT_ID',
      },
      //optionally override the firebase version used by the service worker
      firebaseVersion: 'FIREBASE_VERSION_NUMBER', //e.g., '8.1.1'
      //optionally disables development service worker
      disableDevelopment: true, 
      //optionally tells plugin to help unregistering/removing service worker
      removeFirebaseServiceWorker: true,
    },
  },
]

Options:

Note: Aside from config, all of these are optional.

firebaseVersion:

By default, this plugin uses the firebase version from your yarn.lock or package-lock.json file. However, you can set a specific firebase version using this option.

disableDevelopment:

Use this option to tell gatsby-plugin-firebase-messaging not to create a service worker file for development builds. Additionally, setting this option to true will unregister currently registered Firebase service workers in development environments.

removeFirebaseServiceWorker:

Should you decide you no longer want to use Firebase messaging in your app, and you don't want to leave a "stale" service worker registered for whatever reason, leave the plugin installed and set the removeFirebaseServiceWorker option to true. This will allow gatsby-plugin-firebase-messaging to unregister your users from the firebase messaging service worker.

When using this option, you can remove config from the plugin options if you wish.

Using with gatsby-plugin-offline or other service workers

Just use it. Everything works. No additional configuration needed on either end.