A modern web application that helps users find recipes based on available ingredients and food types. Built with React, TypeScript, and Supabase.
- User authentication and profiles
- Ingredient-based recipe search
- Food type filtering
- Favorite recipes management
- Responsive, modern UI
- Dark mode support
- React.js with TypeScript
- Tailwind CSS for styling
- Supabase for backend and authentication
- React Router for navigation
- Framer Motion for animations
- DaisyUI for UI components
- Node.js (v14 or higher)
- npm or yarn
- Supabase account and project
- Clone the repository:
git clone <repository-url>
cd kitchen-chef- Install dependencies:
npm install- Create a
.envfile in the root directory and add your Supabase credentials:
VITE_SUPABASE_URL=your_supabase_url
VITE_SUPABASE_ANON_KEY=your_supabase_anon_key
- Start the development server:
npm run dev- Create a new Supabase project
- Set up the following tables:
- id (uuid, primary key)
- username (text)
- email (text)
- created_at (timestamp)
- id (uuid, primary key)
- title (text)
- description (text)
- instructions (json)
- image_url (text)
- food_type (text)
- created_at (timestamp)
- id (uuid, primary key)
- name (text)
- created_at (timestamp)
- recipe_id (uuid, foreign key)
- ingredient_id (uuid, foreign key)
- measurement (text)
- created_at (timestamp)
- id (uuid, primary key)
- user_id (uuid, foreign key)
- recipe_id (uuid, foreign key)
- created_at (timestamp)
kitchen-chef/
├── src/
│ ├── components/ # Reusable UI components
│ ├── context/ # React Context providers
│ ├── lib/ # Utility functions and configurations
│ ├── pages/ # Page components
│ └── types/ # TypeScript type definitions
├── public/ # Static assets
└── ...config files
npm run dev- Start development servernpm run build- Build for productionnpm run preview- Preview production buildnpm run lint- Run ESLintnpm run test- Run tests
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
This project is licensed under the MIT License - see the LICENSE file for details.
- Supabase for the backend infrastructure
- Tailwind CSS for the styling system
- DaisyUI for UI components
- React Router for routing
- Framer Motion for animations
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:
- Configure the top-level
parserOptionsproperty like this:
export default tseslint.config({
languageOptions: {
// other options...
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
},
})- Replace
tseslint.configs.recommendedtotseslint.configs.recommendedTypeCheckedortseslint.configs.strictTypeChecked - Optionally add
...tseslint.configs.stylisticTypeChecked - Install eslint-plugin-react and update the config:
// eslint.config.js
import react from 'eslint-plugin-react'
export default tseslint.config({
// Set the react version
settings: { react: { version: '18.3' } },
plugins: {
// Add the react plugin
react,
},
rules: {
// other rules...
// Enable its recommended rules
...react.configs.recommended.rules,
...react.configs['jsx-runtime'].rules,
},
})