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

@sodra/parcel-plugin-precache-manifest

v3.1.1

Published

A simple Parcel plugin that generates a precache manifest that can be imported by service workers

Downloads

1

Readme

parcel-plugin-precache-manifest

A simple Parcel plugin that generates a precache manifest that can be imported by service workers

Usage

The plugin generates a file similar to the following:

self.__precacheManifest = {
  "files": ["/index.html", "/client.33316f76.js", "/sw.js"],
  "ver": "a2eeefb1213a80f101f9d6f8687f5007"
}

All parameters have aliases. If you see inconsistencies in these docs, it's probably fine; you can use multiple names for one value.

The files key is a list of files to cache (paths depend on publicURL given to Parcel). ver is a hash of the build and will change itself if you ever update your app. It's useful for purging old cache when updating the client from a service worker.

The filename defaults to precache-manifest.js and the variable name defaults to __precacheManifest (like Workbox-based systems). However, you can customize this in package.json.

In service-worker.js:

importScripts('/myFilename.js'); // path depends on publicUrl param given to Parcel 

self.addEventListener("install", e => {
  // Array containing URLs of everything in the bundle is added to global scope of service worker in precache-manifest.js
  e.waitUntil(caches.open(myVariableName.ver).then(cache => cache.addAll(myVariableName.files)));
});

In package.json:

{
  "precacheManifest": {
    "filename": "myFilename.js",
    "variableName": "myVariableName"
  }
}

If you're want to completely guarantee that you don't use an old version of the manifest when updating your service worker, you can't (yet) use importScripts. However, you can set the option asJSON to true in package.json and make a fetch call instead. This has the added benefit of not adding an extra variable to the global scope. asJSON changes the default filename to precache-manifest.json, and the variableName parameter is no longer allowed.

In service-worker.js:

self.addEventListener("install", e => {
  e.waitUntil(fetch("/precache-manifest.json", { cache: "no-store" })
    .then(res => res.json())
    .then(manifest => caches.open(manifest.ver).then(cache => cache.addAll(manifest.files)))
  );
});

In package.json:

{
  "precacheManifest": {
    "asJSON": true
  }
}

Possibly the ultimate solution is to use the "inject" mode. It inserts the manifest at the top of the service worker, eliminating a need for an "importScripts" call. It's actually quite similar to Workbox Build inject mode. You provide either the filename for the service worker in the out directory or just true to automatically detect the SW.

In service-worker.js:

self.addEventListener("install", e => {
  caches.open(__precacheManifest.ver).then(cache => cache.addAll(__precacheManifest.files));
});

In package.json:

{
  "precacheManifest": {
    "inject": true
  }
}

License

MIT