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

@vtex/gatsby-plugin-onesignal

v1.5.21-avon.0

Published

Gatsby plugin for a simple OneSignal use case.

Downloads

769

Readme

@vtex/gatsby-plugin-onesignal

A simple Gatsby plugin to add OneSignal integration into your Gatsby site.

Install

To install this plugin, simply run:

yarn add @vtex/gatsby-plugin-onesignal

or

npm install @vtex/gatsby-plugin-onesignal

Configuration options and defaults

To make this plugin easy to use and fast to setup, we're using the "Typical Site" integration that OneSignal offers along with customized service worker paths and filenames, to avoid any conflicts with existing service workers your site may already have.

Make sure you have the following selected in your OneSignal admin panel:

OneSignal Web Configuration admin panel

Also, in the advanced section, we're using a few default values that you should change to make this plugin work as is:

OneSignal Web Configuration admin panel (advanced section)

Assuming your OneSignal setup is correct, you're going to receive an appId for your site. This appId is the only required option for this plugin to work, so you should add this to your site's gatsby-config.js file:

  plugins: [
    {
      resolve: `@vtex/gatsby-plugin-onesignal`,
      options: {
        oneSignalAppId: "YOUR-APP-ID-HERE"
      },
    },
  ]

Here's a list of all available options for this plugin and their default values:

| Prop name | Type | Description | Default value | | --------- | -------- | ------------------------------------------------------------- | ------------- | | oneSignalAppId | string | Your OneSignal appId. This option is always required. | undefined | | pathToOneSignalFiles | string | This should match the Path to service worker files option found in the advanced section of your site's OneSignal admin panel. In most cases this should also match the Service worker registration scope option. | "push/onesignal" | | mainSWFileName | string | This should match the Main service worker filename option found in the advanced section of your site's OneSignal admin panel. | "onesignalsdkworker.js" | | updaterSWFileName | string | This should match the Updater service worker filename option found in the advanced section of your site's OneSignal admin panel. | "onesignalsdkupdaterworker.js" |