Next.js 10

#1

Post by ihuman » Tue, Oct 27, 2020, 4:02 PM UTC

Next.js 10
nextjs.org

Re: Next.js 10

#2

Post by ihuman » Tue, Oct 27, 2020, 4:17 PM UTC

They're talking about all the changes right now in Next.js Conf's keynote: https://www.youtube.com/watch?v=1-NzQ9ObsfM

Re: Next.js 10

#3

Post by vvoyer » Tue, Oct 27, 2020, 4:17 PM UTC

Highlights (live from keynote):

- On-demand image optimization, lazy loading, via an Image component (responsive sizes, formats)

- Internationalization support (routing via domain or subpath)

- Next.js analytics. Automated performance testing and tracking https://nextjs.org/analytics

- Next.js commerce. Starter kit for high-performance ecommerce https://nextjs.org/commerce

Blog post: https://nextjs.org/blog/next-10

Full changelog: https://github.com/vercel/next.js/releases/tag/v10.0.0

Re: Next.js 10

#4

Post by kissgyorgy » Tue, Oct 27, 2020, 4:26 PM UTC

There is an online Next.js conference right now: https://nextjs.org/conf/stage/n

Re: Next.js 10

#5

Post by chaostheory » Tue, Oct 27, 2020, 4:26 PM UTC

It's nice to see that Next has Typescript support.

No matter how nice a framework looks, it's a deal breaker when there's no TS support. It's just too hard dealing with a large Javascript code base.

Re: Next.js 10

#6

Post by aloukissas » Tue, Oct 27, 2020, 4:27 PM UTC

Prediction: Google buys Vercel, kills Angular, steps further into e-commerce

Re: Next.js 10

#7

Post by HendrikR » Tue, Oct 27, 2020, 4:31 PM UTC

aloukissas wrote: post #6

Prediction: Google buys Vercel, kills Angular, steps further into e-commerce

… and people would look into https://svelte.dev which might be everything you need.

Re: Next.js 10

#8

Post by tootie » Tue, Oct 27, 2020, 4:31 PM UTC

aloukissas wrote: post #6

Prediction: Google buys Vercel, kills Angular, steps further into e-commerce

Roll it into Firebase maybe

Re: Next.js 10

#9

Post by flak48 » Tue, Oct 27, 2020, 4:31 PM UTC

Is support for nested routes going to be added any time soon?

If I don't want a full page reload when clicking a new tab for example? Or if I want to implement the age old header, sidebar main content layout without importing the header/sidebar in all my routes/components?

I'm aware there are hacks to get around this but would be nice if the standard next router supported nested routing with persistent layouts for those who need it : https://github.com/vercel/next.js/issues/8193

Re: Next.js 10

#10

Post by pier25 » Tue, Oct 27, 2020, 4:31 PM UTC

The big elephant in the room most of these frameworks are missing is partial hydration. Instead of hydrating the whole page, only the interactive parts are hydrated, sending the absolutely minimal JS needed to the client.

AFAIK only Marko has this feature today. Since it's developed and used at Ebay they focused on the best SSR+hydration experience from the start.

Imba v2 will also have patial hydration (confirmed by the devs here on HN).

Other than those two, it seems nobody is really taking partial/progressive/lazy hydration seriously. IMO SSR+partial hydration is really the next frontier in web development.

It's possible to do it yourself (I did it recently with a Svelte project) but it results in complicated setups. We need a solution that does it transparently, extracting the needed components and data automatically.