https://github.com/hiswe/service-worker-test
https://github.com/hiswe/service-worker-test
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/hiswe/service-worker-test
- Owner: Hiswe
- License: mit
- Created: 2018-01-26T12:16:53.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2018-01-26T15:09:38.000Z (over 8 years ago)
- Last Synced: 2025-02-03T22:32:52.766Z (over 1 year ago)
- Language: HTML
- Size: 3.45 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
**Table of Contents** *generated with [DocToc](https://github.com/thlorenz/doctoc)*
- [service-worker-test](#service-worker-test)
- [current browser setup for https](#current-browser-setup-for-https)
- [in chrome:](#in-chrome)
- [in firefox:](#in-firefox)
- [building & launching](#building--launching)
- [custom service worker](#custom-service-worker)
- [using google workbox](#using-google-workbox)
- [issues](#issues)
# service-worker-test
a simple test to see how it differs from using workbox & writting it's own
## current browser setup for https
We need to let the browsers serve the app throught https. Thanks to this [simple guide we have ](https://improveandrepeat.com/2016/09/allowing-self-signed-certificates-on-localhost-with-chrome-and-firefox/)
### in chrome:
```
chrome://flags/#allow-insecure-localhost
```
should be checked
### in firefox:
just add an exceptions for the website
## building & launching
`npm install` then:
### custom service worker
```
npm run serve:custom
```
will run on [https://localhost:3500](https://localhost:3500)
### using [google workbox](https://developers.google.com/web/tools/workbox/)
```
npm run serve:workbox
```
will run on [https://localhost:3600](https://localhost:3600)
## issues
on `chrome` the custom script isn't reliable for an unfound reason…
Getting this strange error:
```
Failed to fetch
```