How dipstick713/nekomi works
Main components
• Frontend (Nuxt 3 SPA)
• Vue components (pages/, components/, app.vue)
• Composables (composables/user.ts)
• Middleware (middleware/auth.ts)
• Backend services (Supabase)
• Authentication (Supabase OAuth integration)
• Database (PostgreSQL tables: users, songs, votes, playlists, members)
• Realtime (WebSocket/Realtime subscriptions)
• External API (Spotify)
• OAuth token endpoint
• Search & metadata endpoints
• Hosting/Deployment
• Static assets (public/) served by Vercel/Netlify or CDN
• Environment configuration (.env)
Relationships and data flows
• Browser ↔ Nuxt frontend
• User loads SPAs, navigates pages, triggers UI events.
• Nuxt frontend ↔ Supabase client SDK
• Auth flows (sign-in via Spotify OAuth redirect)
• CRUD on playlists, songs, votes via REST/Realtime
• Realtime subscriptions push updates to UI
• Nuxt frontend ↔ Spotify Web API
• Fetch user profile, track metadata, search results
• Supabase Realtime → Nuxt frontend
• Push vote / song addition / leaderboard changes
• Environment (.env)
• Holds SUPABASE_URL, SUPABASE_KEY, SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET
Architectural patterns & design principles
• Single Page Application (SPA) pattern via Nuxt 3
• Composable-based state management (Vue 3 Composition API)
• Middleware for route protection (auth guard)
• Event-driven updates via Supabase Realtime (Pub/Sub)
• Third-party integration pattern (Spotify OAuth + REST calls)
Final touch points
1. User logs in
2. Create playlist
3. /vote songs
4. Real-time UI updates
• Components, services, and flows from the file tree / README (e.g., middleware/auth.ts, composables/user.ts, pages folder, Supabase tables) are represented.