fix: add predev script to resolve @repo/email import error

[koistya]

Summary

Adds a predev script to the API workspace that automatically builds the email package before starting the development server. This resolves the "Cannot find module '@repo/email'" error that occurs when developers fresh clone the repository and run bun dev without manually building the email package first.

Fixes #2112 (introduced in #2110)

Changes

• Added predev script - "predev": "bun --filter @repo/email build" to apps/api/package.json
• Package dependency updates - Updated multiple dependencies across workspaces:
  • AI SDK: @ai-sdk/[email protected], [email protected] - Latest AI SDK releases
  • Better Auth: [email protected] - Changelog
  • React Email: @react-email/[email protected], @react-email/[email protected], [email protected]
  • Wrangler: [email protected] - Changelog
  • TypeScript ESLint: @typescript-eslint/*@8.43.0 - Release notes
  • Vite: [email protected] - Changelog
  • Other: [email protected], @cloudflare/[email protected], [email protected]

Problem

When users clone the repository and run bun dev, the API server fails to start with:

error: Cannot find module '@repo/email' from 'apps/api/lib/email.ts'

This happens because:

• The API imports email templates from @repo/email
• The email package exports from ./dist/ (compiled TypeScript output)
• The dist folder is gitignored and doesn't exist on fresh clone
• Users had to manually run bun email:build first

Solution

The predev script leverages npm/Bun's lifecycle hooks to automatically build the email package before the dev script runs. This works with both:

• Direct API commands: bun dev (from apps/api/)
• Root shortcuts: bun api:dev (from repository root)

Testing

Verified the fix by:

1. Removing the apps/email/dist folder to simulate fresh clone state
2. Running bun api:dev and bun dev (from API directory)
3. Confirming the predev script builds the email package automatically
4. Verifying the API starts without errors

Result: Developers can now run bun dev immediately after cloning without any manual setup steps.

Code Quality Integration

lint-staged Configuration: The repository uses lint-staged with Husky pre-commit hooks for automated code quality checks:

• Pre-commit hook: Runs bunx lint-staged on all staged files
• ESLint: Validates JavaScript/TypeScript files with zero warnings policy
• Prettier: Ensures consistent formatting across all files
• File patterns: Covers *.{js,jsx,ts,tsx,mjs,cjs} for linting and * for formatting

This integration ensures all commits maintain consistent code style and pass linting rules before reaching the repository.