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

grunt-workbox

v1.0.3

Published

Grunt plugin for integrating Workbox

Downloads

1,119

Readme

grunt-workbox

Grunt plugin for integrating Workbox

Grunt

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-workbox --save-dev

One the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-workbox');

Tasks

Overview

In your project's Gruntfile, add a section named generateSW, injectManifest or copyWorkboxLibraries to the data object passed into grunt.initConfig().

The "generateSW" task

grunt.initConfig({
    generateSW: {
        default: {
            swDest: 'dist/web/sw.js',
            globDirectory: 'dist/web',
            globPatterns: ['**/*.{js,css,html,png}']
        }
    }
})

This task creates a list of URLs to precache, referred to as a "precache manifest", based on the options you provide.

It also takes in additional options that configures the service worker's behavior, like any runtimeCaching rules it should use.

Based on the precache manifest and the additional configuration, it writes a ready-to-use service worker file to disk at swDest.

The options for this task are documented in the Workbox Reference Docs. Please read their documentation carefully.

The "injectManifest" task

grunt.initConfig({
    injectManifest: {
        default: {
            swSrc: 'dist/web/sw.js.template',
            swDest: 'dist/web/sw.js',
            injectionPoint: '<% MANIFEST FILES %>',
            globDirectory: 'dist/web',
            globPatterns: ['**/*.{js,css,html,png}']
        }
    }
})

This task creates a list of URLs to precache, referred to as a "precache manifest", based on the options you provide.

The manifest is injected into the swSrc file, and the placeholder string injectionPoint determines where in the file the manifest should go.

The final service worker file, with the manifest injected, is written to disk at swDest.

The options for this task are documented in the Workbox Reference Docs. Please read their documentation carefully.

The "copyWorkboxLibraries" task

grunt.initConfig({
    copyWorkboxLibraries: {
        default: {
            destDirectory: 'dist/web',
        }
    }
})

This task copies over a set of runtime libraries used by Workbox into a local directory, which should be deployed alongside your service worker file.

As an alternative to deploying these local copies, you could instead use Workbox from its official CDN URL.

This method is exposed for the benefit of developers using injectManifest() who would prefer not to use the CDN copies of Workbox. Developers using generateSW() don't need to explicitly use this task.

The options for this task are documented in the Workbox Reference Docs. Please read their documentation carefully.