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

service-worker-admin

v0.2.2

Published

manager for service workers using json and manifest files

Downloads

8

Readme

service-worker-admin

manager for service workers using json and manifest files

Desarrollo

Hasta acá tenemos un service-worker.js genérico (lo cual no sé si es la mejor idea porque Matt Gaunt dice que el mecanismo de actualización se basa en el cambio sobre este archivo, además todos los ejemplos tienen la lista a cachear acá dentro). De todos modos eso se puede cambiar después usando templates que pisen la lista dentro del código.

La API se basa en que parte del conocimiento lo tiene el cliente (la dirección del "manifiesto" y el nombre de la aplicación). El uso sería así:

var swa = new ServiceWorkerAdmin2()
swa.installOrActivate({
    onInstalling:()=>{
        document.getElemntById('installing').style.display='';
    },
    onInstalled:async ()=>{
        var confirm = await confirm('Ready to run. Reload?');
        return confirm; // si contesta TRUE sw hace el reload
    },
    onActive:()=>{
        // solo se llama si estaba instalado previamente después del reload
        document.getElemntById('main-app').style.display='';
        startApp();
    }
})