This forces a fresh Vercel deployment so it builds the latest commit — Vercel's deploy hook didn't pick it up on its own.

React + Vite

This template provides a minimal setup to get React working in Vite with HMR and some Oxlint rules.

Currently, two official plugins are available:

• @vitejs/plugin-react uses Oxc
• @vitejs/plugin-react-swc uses SWC

React Compiler

The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.

Expanding the Oxlint configuration

If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and Oxlint's TypeScript related rules in your project.

Optional: AI chat assistant (Claude)

The app includes an in-app AI chat (the 💬 button) that can see the student's upcoming exams, study goals, and energy level to give personalized advice. It talks to Anthropic's Claude API through a small local backend, so your API key never reaches the browser.

1. Get an API key at console.anthropic.com.
2. Copy server/.env.example to server/.env and paste your key into ANTHROPIC_API_KEY=. Never commit this file (it's already in .gitignore) or paste a real key into .env.example.
3. Run npm run dev:full instead of npm run dev — this starts both the Vite dev server and the chat backend together.
4. If you don't set up a key, the rest of the app works exactly as before; the chat button will just show an error explaining the key is missing.

Note: the chat only works when running the app with its own backend (npm run dev:full, or your own hosting of both server/ and the built frontend). It will not work from a static, backend-less deployment of the built files alone.

Optional: real push notifications

The bell icon's "Enable phone notifications" option sends real OS-level push notifications (streak reminders, upcoming-exam nudges, your custom reminders) on a schedule — even while the app/tab is closed, using the browser's Push API + a small backend (server/index.js) that already exists for the AI chat.

1. Generate your own VAPID key pair once: npx web-push generate-vapid-keys.
2. In server/.env, set VAPID_PUBLIC_KEY and VAPID_PRIVATE_KEY to that pair, and VAPID_CONTACT to a mailto: address. Optionally set PUSH_INTERVAL_MINUTES (default 60) to control how often it checks.
3. Run npm run dev:full (same as the AI chat — both share this backend).
4. Open the bell menu in the app and tap "Enable phone notifications"; grant the browser's permission prompt.

Limitations to know about:

• Only works while running with the backend (npm run dev:full or your own hosting of server/ + the built frontend) — not from the static demo build alone.
• On a phone, reliability (especially on iOS) is much better if you add the site to the home screen first.
• Whether a notification actually reaches a sleeping phone still depends on the OS/browser's own battery and background-activity rules — this isn't a guarantee the way a native app's push service is.

Deploying to production (Vercel)

Google/Apple sign-in, Supabase sync, and the AI features all need a real backend origin — they cannot run from a sandboxed preview (e.g. a Claude Artifact), which blocks both third-party login redirects and most outbound network calls. Deploying to real hosting removes both restrictions.

The api/ folder holds the same backend logic as server/index.js, packaged as individual Vercel Serverless Functions (api/chat.js, api/plan/*.js, api/push/*.js) — Vercel detects the Vite frontend and these functions automatically, no extra config beyond vercel.json (already included, for the push-notification cron schedule).

1. Push this repo to GitHub (if it isn't already).
2. Create a free account at vercel.com (sign in with GitHub is easiest) and click "Add New… → Project", then import this repo.
3. Before the first deploy, add these under Project Settings → Environment Variables (Production, and Preview if you want preview deploys to work too):
   • VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY — same values as your local .env.
   • ANTHROPIC_API_KEY (and optionally ANTHROPIC_MODEL) — same as server/.env.
   • SUPABASE_SERVICE_ROLE_KEY — from Supabase's Project Settings → API → "service_role" secret key (needed for deleting an account — which the App Store requires — and for push notifications; see server/.env.example).
   • After adding or changing variables, redeploy (Deployments → ⋯ → Redeploy). Open /api/chat on the live site to check: it shows {"ai": true, "accounts": true} when the AI key and Supabase are set.
   • VAPID_PUBLIC_KEY, VAPID_PRIVATE_KEY, VAPID_CONTACT — same as server/.env, if you want push notifications.
   • CRON_SECRET — any random string, if you set up push notifications (locks down the cron endpoint; see server/.env.example).
4. Click Deploy. Once it's live, add Supabase's real deployed URL to Authentication → URL Configuration → Redirect URLs in your Supabase project (otherwise OAuth sign-in will redirect back to the wrong place).
5. Every git push to your default branch redeploys automatically.

Note on push notifications: Vercel has no long-running process to hold a timer in, so scheduled sends run via Vercel Cron (vercel.json) hitting /api/push/cron instead of the setInterval loop used locally. Cron frequency limits differ by Vercel plan — check your dashboard/plan's current limits if vercel.json's hourly schedule isn't accepted, and adjust it.