How masantillan/tracker works
This is a browser-based expense tracker: a user submits or deletes an expense, and the screen refreshes to show that day’s expenses and total. The app validates and formats amounts, while a separate module persists expenses in IndexedDB and filters them by local day. A service worker provides a cache-first path for GET requests, falling back to the network. The excerpts show these runtime behaviors; the HTML and manifest were not sampled, so their wiring and any additional capabilities are not represented.
Main entry points: sw.js Service worker · app.js Expense screen and actions · db.js Expense persistence
Components 7
Expense tracking
- Expense screen and actions
js/app.js - Expense persistence
js/db.js
Offline support
- Service worker
sw.js
Other components
- User
- IndexedDB
- Cache Storage
- Network
Connections 5
- User → Expense screen and actions: submits or deletes
js/app.js - Expense screen and actions → Expense persistence: adds, lists, deletes
js/app.js - Expense persistence → IndexedDB: reads and writes
js/db.js - Service worker → Cache Storage: checks cache
sw.js - Service worker → Network: fetches on miss
sw.js