Upgrade dependencies: Base UI, Drizzle v1, better-auth improvements

[Enalmada]

Summary

Major dependency upgrades and improvements:

• Base UI migration: Replaced Radix UI primitives with Base UI components for better maintainability
• Drizzle ORM v1 beta: Upgraded to drizzle-orm@1.0.0-beta.10 with new RQBv2 relations syntax
• better-auth improvements:
  • Switched to better-auth/minimal for smaller bundle size
  • Added @better-auth/drizzle-adapter from PR #6913 for Drizzle v1 compatibility
  • Fixed cookie forwarding for session refresh
• TanStack Form: Added form utilities and components
• Removed unused dependencies: next-themes, @enalmada/drizzle-helpers

Key Changes

• Updated E2E test setup to run migrations before tests
• Centralized Drizzle relations in relations.ts using defineRelations
• Updated buildWhereClause for Drizzle v1 RQBv2 object-based filters

Known Limitations

• experimental.joins is disabled in better-auth config until the drizzle adapter PR fully supports Drizzle v1 RQBv2 relations

Test plan

• TypeScript type checking passes
• Biome linting passes
• Unit tests pass (62 tests)
• E2E tests pass (15 tests)
• Manual testing: user creation and authentication works

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9b46c9e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[gemini-code-assist]

Summary of Changes

Hello @Enalmada, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a significant technical refresh, upgrading core dependencies and migrating UI components to enhance maintainability, improve performance, and streamline the development workflow. Key updates include transitioning from Radix UI to Base UI for a more modern component architecture, upgrading Drizzle ORM to its latest beta with improved relation handling, and integrating TanStack Form for a more robust form management solution. These changes aim to modernize the codebase and align with current best practices in web development.

Highlights

• Base UI Migration: Replaced existing Radix UI primitives with Base UI components, adopting the 'base-vega' style for shadcn/ui. This involved updating component usage from asChild to render props, adjusting styling, and modifying test queries for checkbox elements. A dedicated migration guide (src/components/ui/RADIX_MIGRATION.md) has been added to detail these changes.
• Drizzle ORM v1 Upgrade: Upgraded Drizzle ORM to v1 beta, introducing the new RQBv2 relations syntax. This required centralizing relation definitions in a new src/server/db/schema/relations.ts file and updating the buildWhereClause utility to support object-based filters. Database migrations were also updated to reflect schema changes and new foreign key conventions.
• Better-Auth Improvements: Updated better-auth to use the minimal bundle for a smaller size and integrated the @better-auth/drizzle-adapter for Drizzle v1 compatibility. Session handling was improved to correctly forward Set-Cookie headers for session refreshes.
• TanStack Form Integration: Introduced TanStack Form utilities and components, replacing the previous React Hook Form setup. This includes a new src/components/ui/tanstack-form.tsx file and removal of the old src/components/ui/form.tsx.
• Dependency Management: Performed a major update of various dependencies, including @tanstack/react-router, @tanstack/react-start, @biomejs/biome, and vitest. Unused dependencies like next-themes and @enalmada/drizzle-helpers were removed.
• E2E Test Setup Enhancement: Modified the Playwright E2E test configuration to run Drizzle migrations automatically before tests, ensuring a consistent database state for testing.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a significant set of dependency upgrades, most notably migrating the UI from Radix to Base UI and updating Drizzle ORM to v1. The changes are extensive and appear to be well-executed, with the new RADIX_MIGRATION.md file providing excellent context for the UI changes. The updates to better-auth to improve session handling and the refactoring for Drizzle's new query builder are also solid improvements. My main feedback is a potential regression in the theming of toast notifications, which I've detailed in a specific comment. Overall, this is a very impressive and thorough upgrade.

[gemini-code-assist]

The theme for the Sonner component is now hardcoded to "system". This is a regression from the previous implementation which used useTheme from the now-removed next-themes package. If the application's ThemeToggle allows users to set a theme that differs from their system preference (e.g., forcing dark mode on a light system), the toasts will not match the application's theme. The theme prop should dynamically reflect the application's current theme to ensure visual consistency.