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

easy-web-notifications

v1.0.2

Published

Easy Web Notification registration & handling for Chrome and Firefox browsers

Downloads

6

Readme

easy-web-notifications for Chrome and Firefox

This is a easy to use plugin that will help you save some time in implementing Web Push Notifications in your Client Apps.

Installation:

npm install easy-web-notifications

Setup:

Copy the file PushServiceWorker.js from the plugin directory (./node_modules/easy-web-notifications/) to your public assets directory in your Web App. This file is basically a listener for the incoming notification events.

Then add the following lines to your index.html under <head> tag. (Make sure to edit )

<script>
    if (navigator.serviceWorker) { 
        navigator.serviceWorker.register('<PATH_TO_YOUR_PUBLIC_ASSETS_DIRECTORY>/PushServiceWorker.js')
        .then(function(reg) {
            window.pushReg = reg;
            if (reg.installing) {
                console.info('Service worker installing');
            } else if (reg.waiting) {
                console.info('Service worker installed');
            } else if (reg.active) {
                console.info('Service worker active');
            }
            if (!(reg.showNotification)) {
                console.info('Notifications aren\'t supported on service workers.');
            }
            // Check if push messaging is supported
            if (!('PushManager' in window)) {
                console.info("Push messaging isn't supported.");
            }

            if (Notification.permission === 'denied') {
                console.info('The user has blocked notifications.');
            }
        }).catch(err => {
            console.error(JSON.stringify(err));
        });
    } else {
        console.info("Service workers aren't supported in this browser.");
    }
</script>

Next, create a file named manifest.json in the same directory where you copied PushServiceWorker.js. Copy/Paste the following content into it:

{ "name": "<APP-NAME>", "gcm_sender_id": "<YOUR-FCM-SENDER-ID-HERE>" }

This file is required for sending notifications to Chrome from FCM. Now, link the file to index.html as follows:

<link rel="manifest" href="<PATH_TO_YOUR_PUBLIC_ASSETS_DIRECTORY>/manifest.json">

That's it, you're all set to use the SDK.


This plugin will automatically take care of asking permission to the User for allowing Notification and will also return a Subscription token in case the User has allowed to be notified - all of this in just 1 API call.

All you need to do is call - Push.requestPermissionAndGetToken(VAPID_PUBLIC_KEY);


What is this VAPID?

Voluntary Application Server Identification for Web Push (VAPID) protocol. Chrome browser clearly states that Only VAPID keys will be supported in the future.

To simplify for current understanding, VAPID keys (public and private) are a set of keys to authenticate the communication between desired Push Client (Web Push App) and designated Push Server (Web Push enabled Backend Server).

Check this online VAPID keys generator to get your own set of keys: Click me!

Note - We just need Public VAPID key on the Client App, but we will need both Public and Private VAPID keys for server side implementation.


Usage:

import Push from 'easy-web-notifications';
...
...

const applicationServerPublicKey = "<YOUR_VAPID_PUBLIC_KEY>";
Push.requestPermissionAndGetToken(applicationServerPublicKey).then(res => {
    console.log("Successfully Registered for Push. Token is : \n" + JSON.stringify(res));
}).catch(err => {
    console.log("Push Registration Failed" + err);
});

For any issues, please open a task here.