Love it, and to add to it if i may i think using a blog or profile page (or any dynamic) is clearer than an about page as most of the text in about would be static and most frameworks would i guess ssr it so there would not be a need to 'code split' or lazy load, but a dynamic page would need to execute js. Just putting it out there incase someone thinks its necessary to lazy load text, i know i used to
Next has dynamic which allows you to opt in to code splitting: nextjs.org/docs/pages/building-your-application/optimizing/lazy-loading They also optimize package imports: vercel.com/blog/how-we-optimized-package-imports-in-next-js The next build process also automatically splits your js bundles when possible.
Amazing episode! Well done! Defenitely do more of these!
Great explanation. Thanks CJ!
Amazing video, thank you so much 🙏
Wow! great concise explanation
Syntax is great. Loving these topics 😅😅
great topic! keep them coming
Love it, and to add to it if i may i think using a blog or profile page (or any dynamic) is clearer than an about page as most of the text in about would be static and most frameworks would i guess ssr it so there would not be a need to 'code split' or lazy load, but a dynamic page would need to execute js. Just putting it out there incase someone thinks its necessary to lazy load text, i know i used to
Yes good point. For statically generated sites, it makes less sense to use dynamic.
Does Next.js app router code splitting by default?
Next has dynamic which allows you to opt in to code splitting: nextjs.org/docs/pages/building-your-application/optimizing/lazy-loading
They also optimize package imports: vercel.com/blog/how-we-optimized-package-imports-in-next-js
The next build process also automatically splits your js bundles when possible.