t3-code-android-nightly/.repos/alchemy-effect/examples/aws-website-vite
Julius Marminge 6f9cea00ae
chore(refs): sync Effect and Alchemy references to 4.0.1 and beta.80 (#16170)
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-05 13:22:30 -07:00
..
src chore(refs): sync Alchemy reference to beta.76 (#10654) 2026-09-07 21:54:45 -07:00
test chore(refs): sync Effect and Alchemy references to rc.115 and beta.78 (#12327) 2026-09-17 23:21:25 -07:00
alchemy.run.ts chore(refs): sync Alchemy reference to beta.76 (#10654) 2026-09-07 21:54:45 -07:00
index.html chore(refs): sync Alchemy reference to beta.76 (#10654) 2026-09-07 21:54:45 -07:00
package.json chore(refs): sync Effect and Alchemy references to rc.115 and beta.78 (#12327) 2026-09-17 23:21:25 -07:00
README.md chore(refs): sync Alchemy reference to beta.76 (#10654) 2026-09-07 21:54:45 -07:00
tsconfig.json chore(refs): sync Effect and Alchemy references to 4.0.1 and beta.80 (#16170) 2026-10-05 13:22:30 -07:00
vite.config.ts chore(refs): sync Alchemy reference to beta.76 (#10654) 2026-09-07 21:54:45 -07:00

AWS Website: Vite

Deploys a Vite React SPA to AWS with AWS.Website.Vite — static assets (the vite build output) in S3 behind a CloudFront distribution. No server function is created; the page renders entirely in the browser.

  • src/main.tsx mounts the React app into index.html.
  • Tailwind CSS v4 is wired through @tailwindcss/vite in the project's own vite.config.ts, which Alchemy loads natively — plugins included.
  • spa defaults on, so unmatched paths answer with the index page.

The integration package must be installed in the project (it is loaded dynamically at deploy time):

bun add -d @alchemy.run/frontend-frameworks

Deploy

bun install
bun run deploy

Unchanged sources skip the Vite build entirely on subsequent deploys — the input files are content-hashed (scoped by memo.include).

Local development

bun run dev

alchemy dev runs Vite's own dev server (HMR included) — no cloud resources are created.

Destroy

bun run destroy