How villa-mark/inventory-management-system works
This is an in-development inventory-management application. The README describes the intended user journey—manage products and suppliers, track stock and purchase orders, then review dashboards and reports—but the sampled runtime is only a Hono health/root server and a default SvelteKit page. The graph includes documented product capabilities as planned subsystems; their implementation is not present in the tree. The README documents the UI-to-REST-to-PostgreSQL architecture, but no database connection or feature routes were sampled.
Main entry points: index.ts Hono server · +page.svelte SvelteKit UI · src Products and categories
Components 15
Web client
- SvelteKit UI
frontend/src/routes/+page.svelte - App layout
frontend/src/routes/+layout.svelte
Backend API
- Hono server
backend/src/index.ts - PostgreSQL
Inventory operations
- Products and categories
backend/src - Supplier management
backend/src - Stock movements
backend/src - Purchase orders
backend/src - Inventory dashboard
backend/src - Reports and exports
backend/src - Stock notifications
backend/src
Access and oversight
- Authentication and roles
backend/src - User management
backend/src - Audit history
backend/src
Other components
- Inventory user
Connections 13
- Inventory user → SvelteKit UI: uses
README.md - SvelteKit UI → Hono server: REST requests
README.md - Hono server → PostgreSQL: SQL access
README.md - Hono server → Products and categories: planned API
- Hono server → Supplier management: planned API
- Hono server → Stock movements: planned API
- Hono server → Purchase orders: planned API
- Hono server → Inventory dashboard: planned API
- Hono server → Reports and exports: planned API
- Hono server → Stock notifications: planned API
- Hono server → Authentication and roles: planned API
- Hono server → User management: planned API
- Hono server → Audit history: planned API