How coachemmy/movieers works
Project type and purpose
• Movieers is a full-stack web application:
• Frontend: React single-page app (SPA) with internationalization (i18n) and Tailwind CSS.
• Backend: Node.js/Express server that serves the SPA, provides a REST API, and manages an SQLite database.
• Database: SQLite (movieers.db) for storing user movie lists and any persisted data.
• External Services: Likely a third-party movie data API used by src/services/api.js for movie searches and popular movie data.
File structure
• Top-level:
• public & dist: Static assets and production build of the frontend (dist contains final index.html, robots.txt).
• src: React source code—App.js mounts the SPA; components/ holds UI pieces; pages/ holds route targets; context/ for state management; services/ for API calls; i18n.js for localization.
• server.js & database.js: Express server entry point and database connection/initialization logic (auto-creates schema on startup).
• Configuration files: package.json, tailwind.config.js, postcss.config.js.
• Patterns:
• SPA served by Express.
• React Context for global state (movie list).
• REST endpoints in server.js interacting with the SQLite database.
README for additional insights
• Confirms that starting the server auto-creates the SQLite schema.
• Usage instructions imply a single process runs both the API and static file server.