How codedeficient/audiosphere works
Project type and purpose
• AudioSphere is a full-stack, web-based music player built on Next.js.
• It serves a React-based UI in the browser, provides a Node-based API route for listing audio tracks, and hosts static audio assets and auth handlers via Firebase (deployed on Vercel).
• It leverages Tone.js in the client for real-time audio processing and Nix/GitHub Actions for reproducible builds and CI/CD.
File structure
Top-level directories and files reveal the following logical layers:
• src/app – Next.js App Router folder (page.tsx, layout.tsx, API routes under app/api).
• src/components – React UI components (MusicPlayer, PlaybackControls, SphereVisualizer, Playlist, plus a UI library).
• src/hooks & src/lib – custom React hooks and utility functions.
• public/audio – static audio files.
• public/_auth – static auth handlers/experiments.
• .github/workflows & .github/scripts – CI/CD pipeline and scripts.
• .idx/dev.nix – Nix development shell definition.
Configuration and build files (.eslintrc.json, tsconfig.json, next.config.ts, Tailwind/PostCSS configs, package.json) confirm a Next.js + TypeScript + Tailwind CSS stack.
Extract additional insights from the README
• The project already defines four logical layers: Client, Server/Build, Hosting/Storage, and DevOps.
• Key technologies: Next.js (SSG/SSR), React components, Tone.js (client audio), Firebase Hosting, GitHub Actions, Nix, Vercel deployment.