dropthejase rips out the frontend's foundation and starts over

Louis swaps its entire web framework for a leaner setup - same product, simpler machinery underneath.

infrastructurechat-ui

In one sweeping change, dropthejase moved Louis off Next.js - a heavyweight React framework - and rebuilt the web app on Vite, a faster, lighter build tool, paired with React Router for navigation. The result is a pure browser-side app that ships as static files to Amazon's storage and content-delivery network. The way it deploys doesn't change; what changes is how much framework sits between the code and the browser.

Bundled into the work is a small but real fix: deleting the chat you're currently reading no longer dumps you on a broken page. The team also wired up how the app builds its backend connection at runtime rather than hard-coding it.

So what Mostly plumbing - but worth a look if you're a founder building a legal product on Mike and weighing how heavy your frontend stack needs to be.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from dropthejase/louis, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
5802aa6f Migrate frontend from Next.js to Vite + React Router Jason Lee 2026-05-11 ↗ GitHub
commit body
- Replace Next.js App Router with react-router-dom v7 SPA routing
- Remove all 'use client' directives, next/navigation, next/link imports
- Replace useRouter/usePathname with useNavigate/useLocation
- Replace useSearchParams() call with [searchParams] destructuring
- Add Amplify <Authenticator> as root auth gate, remove custom login/signup pages
- Add AuthProvider inside Authenticator render in App.tsx
- Consolidate Amplify config (including Identity Pool) in lib/aws/config.ts
- Build AgentCore invocation URLs from ARNs at runtime
- Replace NEXT_PUBLIC_* env vars with VITE_* throughout
- Replace uploadData key param with path to avoid public/ prefix
- Add key={id} wrapper on AssistantChatPage for unmount/remount on route change
- Replace process.env.NEXT_PUBLIC_API_BASE_URL with API_URL from config
- Account page uses React Router nested routes for /account/models
- WorkflowPage migrated from next/dynamic to direct import
- TypeScript compiles clean, Vite build succeeds
7845ed46 Add delete-active-chat navigation and env example file Jason Lee 2026-05-11 ↗ GitHub
- SidebarChatItem navigates to /assistant when deleting the active chat
- Add .env.local.example with VITE_* variable names for Vite migration

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-343.md from inside the repo you want the changes in.

⬇ Download capture-thread-343.md