sw-precache - A node module to generate service worker code that will precache specific resources so they work offline

  •        45

Service Worker Precache is a module for generating a service worker that precaches resources. It integrates with your build process. Once configured, it detects all your static resources (HTML, JavaScript, CSS, images, etc.) and generates a hash of each file's contents. Information about each file's URL and versioned hash are stored in the generated service worker file, along with logic to serve those files cache-first, and automatically keep those files up to date when changes are detected in subsequent builds. Serving your local static resources cache-first means that you can get all the crucial scaffolding for your web app—your App Shell—on the screen without having to wait for any network responses.

https://github.com/googlechrome/sw-precache

Dependencies:

dom-urls : ^1.1.0
es6-promise : ^4.0.5
glob : ^7.1.1
lodash.defaults : ^4.2.0
lodash.template : ^4.4.0
meow : ^3.7.0
mkdirp : ^0.5.1
pretty-bytes : ^4.0.2
sw-toolbox : ^3.4.0
update-notifier : ^2.3.0

Tags
Implementation
License
Platform

   




Related Projects

offline-plugin - Offline plugin (ServiceWorker, AppCache) for webpack (https://webpack.js.org/)

  •    Javascript

This plugin is intended to provide an offline experience for webpack projects. It uses ServiceWorker, and AppCache as a fallback under the hood. Simply include this plugin in your webpack.config, and the accompanying runtime in your client script, and your project will become offline ready by caching all (or some) of the webpack output assets.

sw-precache-webpack-plugin - Webpack plugin that generates a service worker using sw-precache that will cache webpack's bundles' emitted assets

  •    Javascript

SWPrecacheWebpackPlugin is a webpack plugin for using service workers to cache your external project dependencies. It will generate a service worker file using sw-precache and add it to your build directory. A simple configuration example that will work well in most production environments. Based on the configuration used in create-react-app.

Workbox: JavaScript libraries for Progressive Web Apps

  •    Javascript

Workbox is a collection of JavaScript libraries for Progressive Web Apps. Workbox is available on npm. We have installation instructions available depending on your build tool or bundler of choice, including webpack. Even on an unreliable connection, your web app can still work using the right runtime caching strategies.

sw-toolbox - A collection of service worker tools for offlining runtime requests

  •    Javascript

Service Worker Toolbox provides some simple helpers for use in creating your own service workers. Specifically, it provides common caching strategies for dynamic content, such as API calls, third-party resources, and large or infrequently used local resources that you don't want precached. Service Worker Toolbox provides an expressive approach to using those strategies for runtime requests. If you're not sure what service workers are or what they are for, start with the explainer doc.

create-react-pwa - https://github

  •    HTML

https://github.com/facebookincubator/create-react-app + Progressive Web App goodness


UpUp - ✈️ Easily create sites that work offline as well as online

  •    Javascript

UpUp is a tiny JavaScript library that makes sure your users can always access your site's content, even when they're on a plane, in an elevator, or 20,000 leagues under the sea. Mobile-First has become the de-facto standard for building modern sites. But in a world where everyone is mobile, an always-on connection isn't something we can rely on. It's time to start thinking Offline First.

vue-wordpress-pwa - An offline-first SPA using Vue

  •    Javascript

This is the code for the FullStackWeekly website. You can use it as a starter pack for your WordPress site as well. Since WordPress can expose a REST API, this project uses Vue.js, Vue-router, Vuex, Vue-resource & Progressive Web App techniques to create an offline-first web client.

next-offline - make your Next.js application work offline using service workers via Google's workbox

  •    Javascript

Use Workbox with Next.js and easily enable offline functionality in your application. Then create a server.js, because we'll need to serve out service worker.

ServiceWorker - The Service Worker Specification https://w3c.github.io/ServiceWorker/

  •    HTML

Service workers are a new browser feature that provide event-driven scripts that run independently of web pages. Unlike other workers, service workers can be shut down at the end of events, note the lack of retained references from documents, and they have access to domain-wide events such as network fetches. Service workers also have scriptable caches. Along with the ability to respond to network requests from certain web pages via script, this provides a way for applications to “go offline”.

offline-first - :electric_plug: Everything you need to know to create offline-first web apps.

  •    

Inspired by the awesome list thing. This specification highlights features (SQL, offline application caching APIs as well as online/offline events, status, and the localStorage API) from HTML5 and provides brief tutorials on how these features might be used to create Web applications that work offline.

application-shell - Service Worker Application Shell Architecture

  •    Javascript

A modern web application architecture leveraging Service Worker to offline cache your application 'shell' and populate the content using JS. This means you can get pixels on the screen without the network, even if the content eventually comes from the network - a great performance win. In browsers without SW, we gracefully degrade to server-side rendering (e.g iOS). Demo. Full details of the architecture can be found in Instant Loading Web Apps With An Application Shell Architecture and Instant Loading with Service Workers.

awesome-service-workers - :nut_and_bolt: A collection of awesome resources for learning Service Workers

  •    

A curated collection of service worker resources. Service workers are at the heart of every progressive web app. Their persistent nature allows progressive web apps to fulfill our expectations of what an app should do. They are the missing link between what only native apps could do and what modern progressive web apps can do.

preact-pwa - Super fast progressive web app with small footprint & minimal dependancies

  •    Javascript

A Super fast progressive web app with a small footprint & minimal dependencies. Features universal rendering, redux, state-driven routing, preact, & service workers. Crunched & optimized with rollup, buble, optimize-js, & purify-css.

expense-manager-demo - Progressive Web App (PWA) demo using Vaadin components

  •    HTML

This is an example project for how you can build a Progressive Web Application with Polymer and Vaadin components. The application uses a Service Worker to cache the Application Shell. A Web App Manifest file ensures that the browser identifies our app as a Progressive Web Application and offers the user to install the application through an install banner.

preact-starter - Webpack3 boilerplate for building SPA / PWA / offline front-end apps with Preact

  •    Javascript

Using preact-starter will kickstart your next application! 💯 It is designed to fit the "90% use-case" for those who want to build offline-first web apps (see features below).

serviceworker-cookbook - It's online. It's offline. It's a Service Worker!

  •    Javascript

A collection of Service Worker use cases, with commented sources and playgrounds.

awesome-pwa - Awesome list of progressive web apps! (PR welcomed ;))

  •    

Inspired by the awesome list thing. A Progressive Web App uses modern web capabilities to deliver an app-like user experience. They evolve from pages in browser tabs to immersive, top-level apps, leveraging the web's low friction.

serviceworker-rails - Use Service Worker with the Rails asset pipeline

  •    Ruby

The Rails asset pipeline makes a number of assumptions about what's best for deploying JavaScript, including asset digest fingerprints and long-lived cache headers - mostly to increase "cacheability". Rails also assumes a single parent directory, /public/assets, to make it easier to look up the file path for a given asset. Service workers may only be active from within the scope from which they are served. So if you try to register a service worker from a Rails asset pipeline path, like /assets/serviceworker-abcd1234.js, it will only be able to interact with requests and responses within /assets/**. This is not what we want.

todo-angular-firebase - Todo app with Angular CLI • AngularFire2 • Firebase • OAuth • SW-Precache

  •    TypeScript

A simple Todo app example built with Angular, Angular CLI and AngularFire2. The app features a Firebase backend with OAuth authentication. Try the demo at ng2-todo-app.firebaseapp.com.





We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.