Why Next.js is Great for Egghead-io
summary
A large legacy Rails monolith with 25 minute builds, hundreds of class components and 1500 tests pushes a rewrite decision toward Next.js; the team runs a proof of concept, moves to TypeScript strict mode, adopts Next.js SSR plus SSG on Vercel, keeps file-system routing and built-in caching, expects much lower Heroku costs and faster developer experience, and publishes the code as egghead-next on GitHub to validate that the approach actually works.
AI-written summary · about
chapters (17)
- 0:00Start
- 2:01A Fresh Start
- 3:01performance
- 3:35build times
- 4:23developer experience
- 4:51state management
- 5:44So many choices...
- 5:57React
- 6:18Gatsby?
- 7:26Full Custom?
- 8:16All in with Next.js!
- 9:08Next.js is Mature
- 9:32Next.js on Vercel gives us best practices for free.
- 10:17Bonus
- 10:32TypeScript
- 10:44Strict mode. No implicit any. ftw
- 11:03Working in the open!
related talks
15mBuilding Isomorphic JavaScript Apps Faster with Next.js
09mBuild Projects 10x Faster with Next.js
39mNavigating front-end architecture like a Neopian
14mRewriting eaze.com with Next.js
12mNext.js at the Edge
18mNext.js - The Hybrid Architecture for Web Developer
10mTaking the Next step
45mNext js: Build a State of the Art E commerce in Fullstack React