Rewriting eaze.com with Next.js
summary
Rewriting eaze.com with Next.js migrates a mobile-first React site onto Next and Now, replacing brittle custom webpack and SSR with reduced webpack code by ~80%, a 12-line server-side render flow, and immutable deploys per PR. Proxying API calls through the front-end removes CORS preflight and saves ~150ms per request. CI runs bundle comparisons with Bundle Cop and Puppeteer e2e screenshots, deployments push updates to users within minutes and measurably improve time-to-interactive.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:10What is Eaze
- 2:12Frontend frameworks before
- 3:41Build infrastructure challenges
- 5:28Why Next.js
- 6:54Server-side rendering improvements
- 8:40Static app and updates
- 9:44API request proxying
- 11:06Client-side performance metrics
- 11:49Tooling with Next.js
- 14:17Summary
related talks
33mUniversal React Apps Using Next.js
34mWhat's Next? Exploring the future of React
45mNext js: Build a State of the Art E commerce in Fullstack React
22mHow micro-frontends and NextJS can 4x site performance
09mBuild Projects 10x Faster with Next.js
10mGradual Migration Strategies for Next.js
31mRethinking composable E-Commerce Frontends
30mComposition, Caching, and Architecture in modern
