I see lot of people happy about NextJS, is there a...
# random
a
I see lot of people happy about NextJS, is there any reason to move from ReactJS? Which use-cases are you guys covering with this framework?
y
We've been pretty happy with NextJS -- their patterns lend themselves well to ecommerce websites that need a mix of static serving content that changes infrequently (collections / products) with that of dynamic client side experiences (think account login / order history)
The store is a shopify store that needed a fresh revamp from it's legacy liquid templating. Going headless provided a lot more flexibility (with the added complexity) but we've learned a ton over the last year.
a
I see, so you take advantage of server-side rendering.
y
Very much so, ISR is a very neat feature that gives us easy flexibility when marking some pages as static (regen every x minutes) vs those that are dynamic
a
Yeah for sure.
y
Vercel does this great out of the box but we couldn't justify the enterprise tier at this point
t
I'm about to start a nextjs project for a blog. Tbh I don't love it but it's extremely good for building things that are more static
a
I like it for SEO.
With other frameworks that’s hard to do.
j
What I find interesting about NextJS is built-in pre-rendering of CSR pages + SSG pages, with one stone. That's cool for SEO. And with SST, you can deploy that and have no lambda actually run. Eventually, I'm curious to see what NextJs does with Server Components.