How ruiji1367/diy-instax-photobooth-vercel works
The tree suggests a browser-based booth product with booth, settings, and camera screens, plus a separate offline spike. The asset names identify these capabilities, but their bundled contents and wiring were not inspected. The only shown runtime logic is the offline service worker, so its cache and network behavior is mapped explicitly; relationships among the application assets are left unspecified.
Main entry points: sw.js Offline Service Worker
Components 12
Booth Interface
- Web App Entry
index.html - App Bundle
assets/index-CGP3v68X.js - Booth Page
assets/BoothPage-DsMx-Fl1.js - Booth Settings
assets/BoothSettingsPage-CYAZ2kUO.js
Camera
- Camera Page
assets/CameraPage-gxQdXVH7.js - Camera Module
assets/camera-qMUGvUY_.js
Offline Support
- Offline Page
offline-spike/index.html - Offline Probe
offline-spike/probe.txt - Offline Service Worker
offline-spike/sw.js - Browser Cache
Other components
- Network
- Browser Runtime
Connections 5
- Offline Service Worker → Browser Cache: pre-caches assets
offline-spike/sw.js - Offline Service Worker → Browser Cache: stores GET responses
offline-spike/sw.js - Offline Service Worker → Network: fetches GET requests
offline-spike/sw.js - Offline Service Worker → Browser Cache: serves on failure
offline-spike/sw.js - Offline Service Worker → Browser Runtime: claims clients
offline-spike/sw.js