How chronie-shizutoki/homemoney works
Project Type and Purpose
• This is a full-stack web application (“Household Finance Manager”) with:
• A Vue 3 SPA frontend (client/)
• An Express/Sequelize/SQLite backend API server (server/)
• Static-hosted mini-applications under client/public/miniapp
• Purpose: enable multilingual personal finance tracking, analytics, budget/debt/todo management and mini-app extensibility.
File Structure
• Top-level “client/” directory houses the Vue 3 application (components, views, router, stores).
• “client/public/miniapp/” contains self-contained micro-apps (calculator, text-encryption-tool) auto-discovered at runtime.
• Top-level “server/” directory houses an Express server:
• src/controllers (request handlers)
• src/models (Sequelize ORM entities)
• src/routes (API endpoints)
• src/utils (response formatters, import/export helpers)
• Config files: vite.config.js (frontend build), server/config/config.js, package.json scripts for dev/build.
• Database migrations/scripts under server/scripts.
README for Additional Insights
• Tech stack: Vue 3, Vite, Element Plus, Pinia, Chart.js, Vue I18n, Axios on frontend; Express, SQLite3, Sequelize on backend; Day.js, Papa Parse for CSVs; bcrypt for encryption.
• Architectural patterns:
• Frontend: component-based UI, composables, Pinia stores, Router.
• Backend: MVC (controllers/models/routes), utility modules for import/export.
• Mini-app subsystem: dynamic scanning of client/public/miniapp, metadata via package.json in each mini‐app.
Detail
• Every major module: router, store, controllers, models, utils, scripts
• Data flows (create/read/update/delete) and analytics pipelines (charts, CSV export/import)
• I18n module connecting to UI text layers
• Build/deploy boundary: Vite dev server vs. production build