-
Notifications
You must be signed in to change notification settings - Fork 0
Feature/better auth migration #103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…pecs - Change specs/archive/ to **/archive/ pattern for broader coverage - Remove outdated feature spec summary document - Remove consolidated brainstorm document (historical reference) - Update README to reflect current documentation structure with requirements.md, design.md, tasks.md, and TESTING.md - Point to archived docs in new location Consolidates learning check documentation to active specs only, moving historical files
- Add comprehensive feature spec for migrating from AWS Amplify to Better Auth - Include requirements.md with user stories, acceptance criteria, and MoSCoW prioritization - Include design.md with architecture, component structure, and security considerations - Include tasks.md with phased implementation breakdown and acceptance criteria - Add README.md documenting spec structure and quick links Covers email/password auth, verification, passwor
- Add auth-schema.ts with user, session, account, and verification tables using Drizzle ORM - Add drizzle.config.ts for PostgreSQL database configuration - Generate initial migration (0000_violet_smiling_tiger.sql) with Better Auth core tables - Add drizzle-kit and drizzle-orm dependencies for database management - Include foreign key constraints with cascade delete for user relationships - Add unique constraints on email and session
- Add new login-form.tsx and signup-form.tsx components using Better Auth patterns - Add field.tsx component library with FieldSet, FieldGroup, FieldLabel, FieldDescription, FieldError, and FieldSeparator - Create /signup page with SignupForm component including name, email, password, and confirm password fields - Update /login page to use new LoginForm component with email and password fields - Remove AuthRedirect wrapper and Sign
…dency - Remove AuthClient.tsx, AuthRedirect.tsx, and SignIn.tsx components using AWS Amplify - Add @radix-ui/react-checkbox dependency for Better Auth form components - Clean up AWS Amplify UI React imports and social provider configurations
…forms - Add authClient initialization using better-auth/react - Implement form state management with email, password, name, and rememberMe fields - Add form submission handlers with error handling and loading states - Connect login form to authClient.signIn.email with remember me checkbox - Connect signup form to authClient.signUp.email with password confirmation validation - Add Checkbox component from Radix UI for remember me functionality - Display
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Remove mock amplify_outputs.json creation from PR checks workflow - Remove conditional TypeScript check logic based on amplify_outputs.json presence in pre-commit script - Simplify build check step by removing Amplify-specific messaging - Make TypeScript check unconditional in pre-commit hook
- Remove amplify.yml build configuration file - Replace AWS Amplify auth with Better Auth session management in middleware - Update /api/user route to use Better Auth session with request headers - Simplify AuthProvider by removing Amplify configuration and Authenticator wrapper - Remove AWS Amplify logic from EmailVerificationHandler component - Update ProtectedRoute to use Better Auth useSession hook instead of useAuthenticator - Simplify SessionHandler by
- Import auth-schema module for database table definitions - Pass authSchema to drizzleAdapter configuration for explicit table mapping
- Group environment variables by category (Core Auth & Database, Mux Video, Tavus Learning Check) - Mark required vs optional sections for better clarity - Add detailed comments for DATABASE_URL format and Tavus webhook configuration - Improve formatting with section separators and consistent spacing - Clarify Tavus webhook usage for Phase 2+ perception/callbacks - Update helper command comments for learning check asset creation
…mponent - Convert dashboard page from client to server component using Better Auth session - Replace AWS Amplify getCurrentUser/fetchUserAttributes with auth.api.getSession - Remove loading state and useEffect in favor of server-side session check - Add redirect to /login when user is not authenticated - Create BackButton component with useRouter for client-side navigation - Replace inline Button with window.history.back() with
Eliminated AWS Amplify-related packages from package.json and removed associated UI component overrides from globals.css. Updated Better Auth migration tasks documentation to include post-migration auth hardening steps.
Changed the Node.js engine version in package.json from '>=20.19.0' to '22.x' to ensure compatibility with Node.js 22.x.
Removed all AWS Amplify related dependencies from package.json and package-lock.json, including aws-amplify, @aws-amplify/adapter-nextjs, @aws-amplify/ui-react, and related devDependencies. Downgraded drizzle-orm and upgraded next to 15.5.9. This cleans up unused AWS Amplify packages and updates project dependencies.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚀 PR Summary
Files Changed: 31
🧪 Testing Checklist
Auto-generated PR description