NextJS - Update to 9.5.X
It's time to update our website that leverages NextJS to the latest release. In this feature experience, I embark on the quick journey of implementing the incremental static regeneration.
- Media available on:
It's time to update our website that leverages NextJS to the latest release. In this feature experience, I embark on the quick journey of implementing the incremental static regeneration.
NextJS 9.5 Release Notes.
About the Tester
The user is me in this case. Some things to note about this log:
- I have collaborated in the FrictionLog website development, focused on the RSS generation for both the podcast and blog feeds, but also some UI work.
- I'm very familiar with JavaScript but not with React.
- I spent ~3 minutes reading the release notes before the recording.
The goal of the log was to update this site with NextJS 9.5.X and implement static site generation. I also decided to validate the trailing slashes feature that shipped with this version.
Logs 5
Delight
Release Notes
The release notes are very easy to understand and read. I know a lot more went into this release but the fact that the highlights are summarized makes the update experience better.
Delight
Time to update
Between the recording and a little more extra work that I did after the overall update process was very fast.
Friction
Component Name Warning
At some point, I noticed a new warning generated by the update of the version. Overall this is a good thing in the sense that the consistency is better in code. I was just not expecting it based on what I knew about the release.
Friction
Dynamically Generated Pages
Not on the video. After I deployed the updated site I noticed that new content (pages) were not dynamically been generated. I focused on both development and testing only on updating content. The implementation was quite simple thanks to the docs.
Friction
Summarized implementation steps
This might be too much of a specific with this release but I lost one of the 2 elements that were needed to implement the goal during the recording. I implemented revalidate in getStaticProps but I missed fallback: true in getStaticPaths.
