Original: https://codingcat.dev/podcast/1-4-next-js-10-with-guillermo-rauch
Since we last talked a year ago
- Zeit became Vercel and gained $21M in funding.
- Vercel’s $40M Series B happened in December.
- Next.js 9 added (to name a few)
- Preview Mode
- Environment Variables
- Fast Refresh
- Static Regeneration
- Next.js Analytics / Commerce
- Next.js 10 released
- next/image
- @next/mdx
Vercel
- We are now using Vercel and Next.js in our next version of codingcat.dev. It has taken me a little bit of getting used to the CI/CD flow coming from Amplify and Google Cloud Build for Firebase hosting. Can you tell me more about Deploy Preview?
- https://rauchg.com/2020/vercel#preview
NextJS
- I have seen a lot of movement to NextJS in the Jamstack community in the last year. What do you think is driving this move from Gatsby to Next? – Brittney
- What is in store for NextJS in 2021? – Brittney
- In browser navigation not working in Firefox and editing in dev tools requires the server to be restarted.
- Images must be in the public folder.
CodingCat.dev on Next.js
Currently we are running on Firebase as a backend with two separate Next.js sites
- Admin – Next.js, React, MaterialUI, backed by Firebase
- Main – Next.js, React, Tailwindcss, backed by Firebase
How can we statically build only our important pages, and then rely on regeneration for the rest? Is it as simple as saying build latest 50 pages and let page props do the rest?
Lighthouse vs. Vercel Analytics how to get 100?
I have read what I will call “way” too much about the Next.js chunks and that Lighthouse complaining about them is basically a non-issue, but is this true?
So in looking at the P99 on Vercel we actually get 100, so what gives, what is this actually showing?
Guillermo Rauch
“Impossible just takes longer”
Top comments (0)