feat: add main application and login routes with UI components

[markbang]

• Implemented the main application route with a layout including a header, folder selection, and writing area.
• Added a login route with a login form and language toggle.
• Introduced TypeScript types for environment variables.
• Updated test setup to remove unnecessary mocks and improve compatibility.
• Refactored theme test utilities to remove dependency on next-themes.
• Adjusted TypeScript configuration for Vite compatibility and included necessary types.
• Created a Vite configuration file with plugins for React, Tailwind CSS, and TanStack.

---

Summary by cubic

Migrated the app from Next.js to Vite + TanStack React Start and added main and login routes with a new shared layout. This improves startup, simplifies routing, and aligns the build output with Tauri.

• New Features

  • Root layout with AppShell and i18n; routes for home (/), dashboard, and login.
  • Lazy-loaded Markdown editor via React.lazy + Suspense in the writing area.
  • Calendar navigation updated with accessible buttons (DayPicker v9).
  • Toast theme follows document light/dark classes (no next-themes).
  • Variable fonts loaded via CSS (Playfair Display, Source Serif 4, JetBrains Mono).

• Migration

  • Switched to Vite, TanStack Router/Start, and Nitro; updated scripts and configs (vite, eslint, tsconfig, postcss).
  • Build output moved to .output; Tauri configured to use it.
  • Removed Next-specific files and deps; added Vite, Tailwind Vite plugin, fontsource, react-day-picker v9.
  • Updated env handling (import.meta.env.DEV) and test setup; added TypeScript env types.

^{Written for commit 03b7b85. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 29 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="package.json">

<violation number="1" location="package.json:73">
P1: Upgrading `react-day-picker` from v8 to v9 will break the Calendar component. The existing code in `components/ui/calendar.tsx` uses v8 API (classNames like `caption_label`, `nav_button_previous`, `day_selected`, etc. and the `Nav` component API). Version 9 has a completely different API that is not backwards compatible. Either keep v8 or update the Calendar component to use v9 API.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P1: Upgrading react-day-picker from v8 to v9 will break the Calendar component. The existing code in components/ui/calendar.tsx uses v8 API (classNames like caption_label, nav_button_previous, day_selected, etc. and the Nav component API). Version 9 has a completely different API that is not backwards compatible. Either keep v8 or update the Calendar component to use v9 API.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At package.json, line 73:

<comment>Upgrading `react-day-picker` from v8 to v9 will break the Calendar component. The existing code in `components/ui/calendar.tsx` uses v8 API (classNames like `caption_label`, `nav_button_previous`, `day_selected`, etc. and the `Nav` component API). Version 9 has a completely different API that is not backwards compatible. Either keep v8 or update the Calendar component to use v9 API.</comment>

<file context>
@@ -58,14 +65,12 @@
-    "next-themes": "^0.4.6",
     "react": "^19.0.0",
-    "react-day-picker": "8.10.1",
+    "react-day-picker": "^9.0.0",
     "react-dom": "^19.0.0",
     "react-hook-form": "^7.55.0",
</file context>

Suggested change

	"react-day-picker": "^9.0.0",
	"react-day-picker": "8.10.1",