How nephwf/kaloriinw works
kaloriiNW is a browser-based calorie and nutrition diary; the README says data stays in localStorage and no server is needed. The main workflow is recording food, water, and activity by day, then reviewing calorie/macronutrient totals and seven-day statistics. The app also supports a product catalog, custom foods, and Mifflin–St Jeor-based targets. The sampled app excerpt shows these responsibilities in app.js, but not all internal calls; the catalog’s use by the app is therefore shown as unverified. Offline caching is implemented by the sampled service worker.
Main entry points: app.js Diary app · sw.js Cache worker · foods.js Food catalog
Components 6
Food diary
- Diary app
app.js - Browser storage
Nutrition data
- Food catalog
foods.js
Offline support
- Cache worker
sw.js - Asset cache
Other components
- Diary user
Connections 5
- Diary user → Diary app: records meals
README.md - Diary app → Browser storage: stores diary
README.md - Diary app → Food catalog: uses catalog
- Cache worker → Asset cache: caches assets
sw.js - Cache worker → Asset cache: serves offline
sw.js