How eyasug/jfit-welness works
The available evidence shows a small PWA caching layer, not the app’s user-facing product workflow: the service worker precaches an app shell and selected CDN resources, then serves navigations and asset requests with cache/network fallbacks. The README is empty and no application source was provided, so the app’s features and service-worker registration path cannot be established.
Main entry points: sw.js Service worker · index.html App shell
Components 5
PWA runtime
- Service worker
sw.js - App shell
index.html - Cache storage
Other components
- Browser
- CDN resources
Connections 4
- Browser → Service worker: dispatches events
sw.js - Service worker → App shell: precaches
sw.js - Service worker → CDN resources: fetches resources
sw.js - Service worker → Cache storage: reads and writes
sw.js