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

sw-precache-list

v0.1.2

Published

Like sw-precache but just generates the precache resource list, allowing you to write your own service worker script

Downloads

6

Readme

sw-precache-list

Precaching that keeps you in control of your service worker.

Want to generate a list of static resources to precache with your service worker?

Want to be able to write your own service worker script?

sw-precache-list may be for you...

Please note, this tool is in progress and probably not suitable for production usage yet.

Example usage

Command line

sw-precache-list 'images/**/*' 'css/*'

NB. If your OS supports globs natively then you could use them directly, e.g. sw-precache-list images/* css/*

As part of your build process

Coming soon...

var swPrecacheList = require('sw-precache-list');

swPrecacheList.write(`${rootDir}/precache-list.js`, ['images/**/*', 'css/*']);

Output

The resulting file (default: precache-list.js) will output the resource list to a global variable called precacheList. You can use it in your service worker script via importScripts. Here is an example:

// service-worker.js

importScripts('precache-list.js');

self.addEventListener('install', function(event) {

  function onInstall () {
    return caches.open('myCacheName')
      .then(function(cache) {
        return cache.addAll( precacheList );
      });
  }

  event.waitUntil(onInstall(event));
});

Or even easier, using sw-toolbox:

importScripts('lib/sw-toolbox.js');
importScripts('precache-list.js');

toolbox.precache(precacheList);

How does this compare to sw-precache?

sw-precache is designed to generate the whole service worker script for you. You cannot manually edit it, because it will get overwritten next time you run it.

sw-precache-list is designed to just generate the precache resource list, which you can use in a service worker that you write yourself.

Still to come

Cache-busting

sw-precache-list is currently very new and simple. It does not yet include cache-busting.

This means that right now you should only use it for static resources that will not be updated (except if you update the filenames).

For more information, see sw-precache's note on cache busting here and Jake Archibald's note here.

We expect to add cache-busting soon, or if you'd like to add it, please submit a PR!

Config

We will also need to add the ability to e.g. strip a directory prefix, to convert local file paths into resource URLs.