How rajeshceg3/fruitninja works
Project type and purpose
• This is a full-stack Next.js application for browsing and filtering a collection of fruits.
• The frontend is built in React (Next.js pages + components), state is managed via a client store, and data is persisted in a SQLite database accessed through Prisma. API routes expose the data to the UI.
File structure
• Top-level folders:
– components/: reusable React UI (BenefitFilter, DaySelector, FruitCard, FruitGrid, Header)
– pages/: Next.js pages (index.js, dynamic [id].js under pages/fruit/, plus API routes under pages/api/)
– prisma/: Prisma schema and development SQLite DB (schema.prisma, dev.db)
– store/: client-side state management (fruitStore.js)
– public/: static assets (images)
– styles/: CSS modules & global styles
– data/: possibly seed/static data (fruits.js)
• Config & scripts: next.config.mjs, jsconfig.json, .eslintrc.json, package.json
README
• Bootstrapped via create-next-app
• Describes dev server, API-route mapping, font optimization, and deployment hints