2dd366172e
## Changes 🏗️ ### Overview Introduces a new responsive `<Dialog />` component that automatically adapts to screen size, providing optimal UX across devices. <img width="800" alt="Screenshot 2025-06-27 at 16 00 01" src="https://github.com/user-attachments/assets/d0c53b30-488f-4102-8100-c9318168d65b" /> <img width="300" alt="Screenshot 2025-06-27 at 16 00 12" src="https://github.com/user-attachments/assets/f2105708-97d9-4a94-8e26-3c2d582ea8cd" /> ### Key Features #### 📱 **Responsive Behavior** - **Desktop**: Modal dialog with overlay - **Mobile**: Bottom drawer [Vaul](https://vaul.emilkowal.ski/) with **swipe-to-dismiss** functionality #### 🎯 **Multiple Interaction Methods** - `ESC` key to close (both desktop & mobile) - Click outside to dismiss - Swipe down to dismiss (mobile drawer) - Close button (X) #### ❓ Why I did not use `shadcn/dialog` in this case as a base While we already use the raw `shadcn/dialog` on the platform, it's designed as a desktop-only solution and is not really responsive-friendly. It lacks 📱 mobile-optimisation patterns like _bottom drawers_, _swipe-to-dismiss gestures_ ( the new implementation has it via [Vaul](https://vaul.emilkowal.ski/) ), and automatic breakpoint adaptation according to screen size. #### 🧩 **Compound Component Pattern** ```tsx <Dialog title="Example"> <Dialog.Trigger> <Button>Open Dialog</Button> </Dialog.Trigger> <Dialog.Content> Content goes here </Dialog.Content> </Dialog> ``` #### ⚙️ **Flexible Control** - **Uncontrolled**: Self-managed state via triggers - **Controlled**: External state management - **Force open**: rare but might be needed - **Custom styling**: if needed ## Checklist 📋 - [x] I have clearly listed my changes in the PR description - [x] I have made a test plan - [x] I have tested my changes according to the test plan: - [x] **Desktop Modal**: Opens/closes via trigger, ESC key, click outside, close button - [x] **Mobile Drawer**: Automatically switches at `lg` breakpoint, swipe-to-dismiss works - [x] **Controlled Mode**: External state management functions correctly - [x] **Force Open**: Dialog stays open for preview purposes - [x] **Custom Styling**: CSS-in-JS overrides work as expected - [x] **Footer Component**: Action buttons render and function properly - [x] **No Title Mode**: Dialog works without title prop - [x] **Accessibility**: Tab navigation, screen reader announcements, ARIA compliance - [x] **Responsive Breakpoints**: Component switches modes at correct screen sizes - [x] **Storybook**: All stories render and function correctly --------- Co-authored-by: Abhimanyu Yadav <122007096+Abhi1992002@users.noreply.github.com>
This is the frontend for AutoGPT's next generation
🧢 Getting Started
This project uses pnpm as the package manager via corepack. Corepack is a Node.js tool that automatically manages package managers without requiring global installations.
Prerequisites
Make sure you have Node.js 16.10+ installed. Corepack is included with Node.js by default.
⚠️ Migrating from yarn
This project was previously using yarn1, make sure to clean up the old files if you set it up previously with yarn:
rm -f yarn.lock && rm -rf node_modulesThen follow the setup steps below.
Setup
-
Enable corepack (run this once on your system):
corepack enableThis enables corepack to automatically manage pnpm based on the
packageManagerfield inpackage.json. -
Install dependencies:
pnpm i -
Start the development server:
pnpm dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
Subsequent Runs
For subsequent development sessions, you only need to run:
pnpm dev
Every time a new Front-end dependency is added by you or others, you will need to run pnpm i to install the new dependencies.
Available Scripts
pnpm dev- Start development serverpnpm build- Build for productionpnpm start- Start production serverpnpm lint- Run ESLint and Prettier checkspnpm format- Format code with Prettierpnpm type-check- Run TypeScript type checkingpnpm test- Run Playwright testspnpm test-ui- Run Playwright tests with UI
This project uses next/font to automatically optimize and load Inter, a custom Google Font.
🚚 Deploy
TODO
📙 Storybook
Storybook is a powerful development environment for UI components. It allows you to build UI components in isolation, making it easier to develop, test, and document your components independently from your main application.
Purpose in the Development Process
- Component Development: Develop and test UI components in isolation.
- Visual Testing: Easily spot visual regressions.
- Documentation: Automatically document components and their props.
- Collaboration: Share components with your team or stakeholders for feedback.
How to Use Storybook
-
Start Storybook: Run the following command to start the Storybook development server:
pnpm storybookThis will start Storybook on port 6006. Open http://localhost:6006 in your browser to view your component library.
-
Build Storybook: To build a static version of Storybook for deployment, use:
pnpm build-storybook -
Running Storybook Tests: Storybook tests can be run using:
pnpm test-storybook -
Writing Stories: Create
.stories.tsxfiles alongside your components to define different states and variations of your components.
By integrating Storybook into our development workflow, we can streamline UI development, improve component reusability, and maintain a consistent design system across the project.
🔭 Tech Stack
Core Framework & Language
- Next.js - React framework with App Router
- React - UI library for building user interfaces
- TypeScript - Typed JavaScript for better developer experience
Styling & UI Components
- Tailwind CSS - Utility-first CSS framework
- shadcn/ui - Re-usable components built with Radix UI and Tailwind CSS
- Radix UI - Headless UI components for accessibility
- Lucide React - Beautiful & consistent icons
- Framer Motion - Animation library for React
Development & Testing
- Storybook - Component development environment
- Playwright - End-to-end testing framework
- ESLint - JavaScript/TypeScript linting
- Prettier - Code formatting
Backend & Services
- Supabase - Backend-as-a-Service (database, auth, storage)
- Sentry - Error monitoring and performance tracking
Package Management
Additional Libraries
- React Hook Form - Forms with easy validation
- Zod - TypeScript-first schema validation
- React Table - Headless table library
- React Flow - Interactive node-based diagrams
- React Query - Data fetching and caching
- React Query DevTools - Debugging tool for React Query
Development Tools
NEXT_PUBLIC_REACT_QUERY_DEVTOOL- Enable React Query DevTools. Set totrueto enable.