NEXT.JS 13 Most impressive Updates you must know about Part 2.

NEXT.JS 13 is a Game Changer.

Before starting. If you want to be the part of CODE Culture Community. Just fill out the form to join the Free Code Culture Sessions and get your questions answered about coding and career. I am form click me

Streaming

The /app directory introduces the ability to progressively render and incrementally stream rendered units of the UI to the client.
With Server Components and nested layouts in Next.js, you’re able instantly to render parts of the page that do not specifically require data and show a loading state for parts of the page that are fetching data. With this approach, the user does not have to wait for the entire page to load before they can start interacting with it.

Data Fetching

Next.js 13 now makes it possible to not use the getServerSideProps() and getStaticProps() method to pass props back and forth. With the introduction of new fetch implementation, you can directly call any API and await for it and it will be server rendered automatically.
Next.js 13 provides one flexible way to fetch, cache, and revalidate data at the component level. This means all the benefits of Static Site Generation (SSG), Server-Side Rendering (SSR), and Incremental Static Regeneration (ISR) are now available through one API.

Turbopack

And last but not the least, the most exciting announcement was the brand build tool called “Turbopack”. Turbopack is supposed to be a Webpack killer and is built on top of Rust, so expect it to be blazingly fast. Just to start with some benchmarks, Turbopack is said to be 700x faster than Webpack. I have covered all about Turbopack in a separate reel, so be sure to check that out for more info.