🏗️(front) replace Next.js with Vite and React Router#607
Conversation
|
Important Review skippedToo many files! This PR contains 102 files, which is 2 over the limit of 100. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (115)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
446db56 to
531530c
Compare
Signed-off-by: Laurent Paoletti <[email protected]>
531530c to
cc70564
Compare
|


Purpose
The frontend was built with Next.js but used almost none of it: no server rendering, no API routes, no server components. It shipped as a static export,which meant paying for the framework build pipeline while getting a plain single-page app in return. That mismatch made the dev server slow to start,the routing conventions confusing, and the trailing-slash behavior of the export leaked into the backend redirect logic.
This replaces the framework with Vite and React Router, which is what the app was already behaving like.
Proposal