-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Any plan on service-worker for offline usage? #771
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
As I just mentioned here, I'm definitely not opposed to adding offline support. 👍 |
I tried hexo-offline with the following configuration: offline:
maximumFileSizeToCacheInBytes: 10485760
staticFileGlobs:
- public/**/*.{js,html,css,png,jpg,gif,svg,eot,ttf,woff}
- public/**/**/*.{js,html,css,png,jpg,gif,svg,eot,ttf,woff}
- public/manifest.json
- public/browserconfig.xml
stripPrefix: public In general, it works, but I was confused by these errors. I also was not able to properly configure caching CDN scripts and Google fonts, it works only through the browser cache. |
CDN scripts should be cached using I will document the usage of I cannot reproduce the error using the given configuration. |
Hi morigs, I've updated the README section to include CDN usage. The I am happy to guide through, don't hesitate to contact me if there is any questions. |
Fixed in #918 |
The hexo-offline supports using
sw-precache
to generate a service worker for offline usage on any hexo site.Browser Support
The text was updated successfully, but these errors were encountered: