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 🙏

© 2026 – Pkg Stats / Ryan Hefner

sw-builder

v1.1.3

Published

The sw-builder package automates the creation of your Application's Service Worker, which pre-caches your build. This leads to a better overall performance and enables users to access your PWA without an Internet connection.

Readme

Service Worker Builder

The sw-builder package automates the creation of your Application's Service Worker, which pre-caches your build. This leads to a better overall performance and enables users to access your PWA without an Internet connection.

Getting Started

Install the package:

npm i -D sw-builder

Create the sw-builder.config.json file in your project's root:

{
  "outDir": "dist",
  "template": "base",
  "includeToPrecache": [
    "/assets",
    "/some-other-dir",
    "/index.html",
    "/logo.png",
    "/splash.png"
  ],
  "excludeFilesFromPrecache": [
    "some-ignorable-file.woff2"
  ],
  "excludeMIMETypesFromCache": [
    "application/json",
    "text/plain",
    "text/html"
  ]
}

Include the sw-builder binary in your package.json file:

...
"scripts": {
  "build": "tsc -b && vite build && sw-builder",
  
  // specify a custom path for the configuration file
  "build": "tsc -b && vite build && sw-builder --config='sw-custom.config.json'",
}
...

If you are using Vite include an empty sw.js file in your public directory so you can test the Service Worker's Registration while developing.

Using the firebase-fcm template

The firebase-fcm template includes the same caching behavior as the base template and appends Firebase Cloud Messaging support to the generated Service Worker.

Update your sw-builder.config.json file to use the firebase-fcm template:

{
  "outDir": "dist",
  "template": "firebase-fcm",
  "includeToPrecache": [],
  "excludeFilesFromPrecache": [],
  "excludeMIMETypesFromCache": [
    "application/json",
    "text/plain",
    "text/html"
  ],
  "firebaseConfigProcessEnvKey": "VITE_FIREBASE_CONFIG",
  "firebaseSdkVersion": "11.0.0"
}

Provide the Firebase Web App options as a JSON string in a process environment variable:

export VITE_FIREBASE_CONFIG='{"options":{"apiKey":"example-api-key","authDomain":"example.firebaseapp.com","projectId":"example-project","storageBucket":"example.firebasestorage.app","messagingSenderId":"123456789012","appId":"1:123456789012:web:example"}}'

The Firebase config variable must be available to the Node process when the command runs. Then pass the environment name to sw-builder:

...
"scripts": {
  "build": "tsc -b && vite build && sw-builder --environment='production'"
}
...

The environment value must be development, staging, or production. It is the only Firebase-related command argument, and it determines the dotenv file name used by the builder: .env, .env.staging, or .env.production.

The generated Service Worker imports the Firebase compat SDK scripts from gstatic, initializes the Firebase app with the provided options, and handles background messages. When app clients are open, messages are posted to them as { type: 'PUSH_MESSAGE', data }. When no app client is open, the Service Worker shows a notification using the title, body, icon, badge, and url fields from the message data. Notification click URLs are limited to the same origin and fall back to the app root URL when missing or unsafe.

Types

The configuration required to build the base template.

type IBaseConfig = {
  // the dir path in which the build's output is placed
  outDir: string;

  // the name of the template that will be generated
  template: "base";

  // the list of asset paths that will be traversed and included in the cache
  includeToPrecache: string[];

  // the list of file names that will be ignored
  excludeFilesFromPrecache: string[];

  // the list of MIME Types that won't be cached when the app sends HTTP GET requests
  excludeMIMETypesFromCache: string[];
};

The options object needed to initialize the Firebase project.

type IFirebaseOptions = {
  apiKey: string;
  authDomain: string;
  projectId: string;
  storageBucket: string;
  messagingSenderId: string;
  appId: string;
}

type FirebaseConfigSchema = {
  options: IFirebaseOptions;
}

The configuration used to build a service working definition that makes use of the firebase-fcm template.

type IFirebaseFcmConfig = {
  outDir: string;
  includeToPrecache: string[];
  excludeFilesFromPrecache: string[];
  excludeMIMETypesFromCache: string[];
  template: "firebase-fcm";
  firebaseConfigProcessEnvKey: string;
  firebaseSdkVersion: string;
}

Built With

  • TypeScript

Tests

# unit and integration tests
npm run test

# unit tests
npm run test:unit

# integration tests
npm run test:integration

License

MIT