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

@edenjs/serviceworker

v2.2.0

Published

[![TravisCI](https://travis-ci.com/eden-js/serviceworker.svg?branch=master)](https://travis-ci.com/eden-js/serviceworker) [![Issues](https://img.shields.io/github/issues/eden-js/serviceworker.svg)](https://github.com/eden-js/serviceworker/issues) [![Licen

Downloads

4

Readme

EdenJS - Serviceworker

TravisCI Issues License Awesome Discord

Serviceworker base logic component for EdenJS

@edenjs/serviceworker automatically adds serviceworker logic to an edenjs install

Setup

Install

npm i --save @edenjs/serviceworker

Configure

config.serviceworker = {
  config : { // this config field is passed to the compiled serviceworker
    offline : { // disable by passing false or null
      files : ['/some/file.png', '/some/otherfile.png', 'https://some.external/file.png'],
    },
  },
};

If offline is on, the entire application can be used offline. To setup routes for offline simply specify @offline as part of their config:

/**
 * Index action
 *
 * @param    {Request}  req
 * @param    {Response} res
 *
 * @view     offline
 * @route    {get} /
 * @layout   main
 * @offline
 */
async indexAction(req, res) {
  // render offline page
  res.render();
}

As we cannot run a function in the backend when the service has no internet, all other features need to be specified in the config rather than the action function. For example, the following will not function in offline mode; while the above will.

/**
 * Index action
 *
 * @param    {Request}  req
 * @param    {Response} res
 *
 * @route    {get} /
 * @offline
 */
async indexAction(req, res) {
  // render offline page
  res.render('offline', {
    layout : 'main',
  });
}

Compilation

Any file you include in the following path will be compiled into the serviceworker:

'public/js/serviceworker.js'
'public/js/serviceworker/**/*'

Messaging

Serviceworker messaging is automated between an installed serviceworker and a global eden object.

Example

In the serviceworker

// set port
const port = null; // can be a sepcific port

// send message to frontend
self.eden.send(port, 'to.send', 'a', 'b');

// receive a request for data from the frontend
self.eden.endpoint('check.something', async (a, b) => {
  // return b
  return b;
});

// receive an event from the frontend
self.eden.on('check.event', async (a, b) => {
  // got event from frontend
  console.log(a, b);
});

In the frontend

// call a serviceworker endpoint
const result = await window.eden.serviceworker.call('check.something', 'a', 'b'); // returns 'b'

// receive a request for data from the frontend
window.eden.serviceworker.send('check.event', 'a', 'b');

// receive an event from the frontend
window.eden.serviceworker.on('to.send', async (a, b) => {
  // got event from serviceworker
  console.log(a, b);
});