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

@sifrr/serviceworker

v0.0.9

Published

Service Worker with customizations.

Downloads

4

Readme

sifrr-serviceworker · npm version Doscify

Customizable Service Worker.

Size

| Type | Size | | :----------------------------------------------------- | :--------------------------------------------------------------: | | Minified (dist/sifrr.serviceworker.min.js) | | | Minified + Gzipped (dist/sifrr.serviceworker.min.js) | |

How to use

Directly in Browser using standalone distribution

Copy contents of sifrr.serviceworker.min.js or sifrr.serviceworker.js in your serviceworker file. And add this at the end of file.

const sw = new Sifrr.ServiceWorker(/* config */);
sw.setup(); // setup service worker caching
sw.setupPushNotification(defaultTitle, defaultOptions); // to setup push event listener

Browser API support needed for

| APIs | caniuse | polyfills | | :----------------- | :----------------------------------------- | :----------- | | Service Worker API | https://caniuse.com/#feat=serviceworkers | Not possible |

Using npm

Do npm i @sifrr/serviceworker or yarn add @sifrr/serviceworker or add the package to your package.json file.

example of sw.js to be bundled (compatible with webpack/rollup/etc):

Commonjs

const SW = require('@sifrr/serviceworker');
const sw = new SW(/* config */);
sw.setup(); // setup service worker caching
sw.setupPushNotification(defaultTitle, defaultOptions); // to setup push event listener
module.exports = sw;
Example here

ES modules

import SW from '@sifrr/serviceworker';
const sw = new SW(/* config */);
sw.setup(); // setup service worker caching
sw.setupPushNotification(defaultTitle, defaultOptions); // to setup push event listener
export default sw;

then in your main js file add:

if ('serviceWorker' in navigator) {
  window.addEventListener('load', function() {
    navigator.serviceWorker.register('sw.bundled.js').then(
      function(registration) {
        // Registration was successful
        console.log('ServiceWorker registration successful with scope: ', registration.scope);
      },
      function(err) {
        // registration failed :(
        console.log('ServiceWorker registration failed: ', err);
      }
    );
  });
}

Config

Default config:

{
  version: 1,
  fallbackCacheName: 'fallbacks',
  defaultCacheName: 'default',
  policies: {
    'default': {
      policy: 'NETWORK_FIRST',
      cacheName: 'default'
    }
  },
  fallbacks: {},
  precacheUrls: []
}
  • version: integer Version of service worker, when you change service worker version old versions' caches will be deleted. All caches are suffixed with -v${version}.
  • fallbackCacheName: string Name of cache storage for fallbacks.
  • defaultCacheName: string Default name of cache storage to be used.
  • policies:
{
  'regex string': {
    policy: 'Name of policy', // default: 'NETWORK_FIRST'
    cacheName: 'Name of cache storage' // default: options.defaultCacheName
  }
}

When a request is sent, if the url matches the regex string then it will be fetched using policy and storaged in cacheName cache storage. The policy with 'default' will be used for urls not matching any regex. Note: Even though regex string is treated as regex, it should be given as a string, eg. '*.js'

  • fallbacks: { 'regex string': 'file url' } If request's url matches regex string (same as policies), then fallback for that url will be file from file url if request is not completed due to no connection, not found, etc. 'default' fallback will be used if no regex matches the url given.
  • precacheUrls: array of string Urls to be precached.

Policies

  • NETWORK_ONLY: Only resolve request from network.
  • NETWORK_FIRST: Try to resolve request from network, if fails then resolve from cache.
  • CACHE_ONLY: Only to resolve request from cache.
  • CACHE_FIRST: Try to resolve request from cache, if fails then resolve from network.
  • CACHE_AND_UPDATE: Send response from cache if available and then updates cache with new network response.

Push Notification

  1. Setup push notification listener in serviceworker using sw.setupPushNotification(defaultTitle, defaultOptions, onNotificationClick), where defaultTitle is default push notification title, defaultOptions are default push notification options and onNotificationClick is fxn that will be executed when user clicks on notification.

  2. In your main JS file use serviceWorkerRegistration object to handle pushNotifications. Simple Example:

if ('serviceWorker' in navigator) {
  window.addEventListener('load', function() {
    navigator.serviceWorker.register('sw.bundled.js').then(
      function(registration) {
        // `registration` is serviceWorkerRegistration object
        // SW registration was successful
        console.log('ServiceWorker registration successful with scope: ', registration.scope);
        registration.pushManager
          .subscribe({
            userVisibleOnly: true,
            applicationServerKey: Uint8ArrayFromPushNotificationServerPublicKey
          })
          .then(function(subscription) {
            // Subscription was successful
            console.log('User is subscribed.');
          })
          .catch(function(err) {
            // Subscription failed
            console.log('Failed to subscribe the user: ', err);
          });
      },
      function(err) {
        // SW registration failed
        console.log('ServiceWorker registration failed: ', err);
      }
    );
  });
}
  1. Send payload from server as a JSON string with title and other options. Example:
{
  "title": "You app name",
  "body": "Notification Body",
  "actions": [
    { "action": "yes", "title": "Yes", "icon": "images/yes.png" },
    { "action": "no", "title": "No", "icon": "images/no.png" }
  ],
  ...
}

More manual configuring

In your sw file

const sw = new SW(/* config */);

// this method will be called when new service worker is available to install
sw.onInstall = () => self.skipWaiting();

// this method will be called when a notification is clicked
sw.onNotificationClick = (event) => event.notification.close();

// You can add methods on self if you need
self.addEventListener(...);

Tutorials