How NextJS REALLY Works

Very nice explanation, Thank you...!

You should do the same for the new version....

I don't think nextjs is normal react app, you are still serving html pages on every subsequent request from server not from browser.

so react is still shipped to client huh

We really need this for app router as well. Especially how navigation works!

Nice explanation. Thank you.

Great explanation! Just not gonna ask any questions to avoid being outright stupid.

Next also has some caching mechanisms that can be good or bad. You don't get that with a regular Vite React SPA.

Either I'm too dumb for cs,Web dev, ,programming 😢 or that this video is for newbies with next cause i didn't get nothing worth watching 26 min of saying next give correct html and react give blank page at first load .

Im i correct 🙁 or did i miss the point wtf🤕🤕

I've been learnig NEXTjs for almost a week reading the Pages Router docs, and there's something that still doesn't make sense in my head.... When a page that was rendered on the server gets to the client as a Loading state or as an UI skeleton, does that mean that the server have a "correct" but empty HTML version of what the user gets after the client fetches and loads the data? Only then the user gets the 2nd correct but complete version of the same HTML page?
Idk if that's clear enough, hopefully it is..

I love how when he tries to demonstrate on twitch how it shows the empty page he can't even get a bad user experience with throttling xD
Shows you how unnecessary and overengineering SSR is

The intro music and clip-of-content before the explanation video starts is gold. You should start doing this again.

life's too short for all this BS. I'm going back to laravel.

awesome video! Thanks 👍🏻

What does React Native do with expo?

Over-explained

Great video! You just earned a sub theo.

we have nest js backend and are looking to move to next js on the front end (from CRA). Server components seem really cool and powerful, but I am trying to wrap my head around how they can be used with an API and without bypassing guards. Any tips?

sick painting

How do you learn stuff like this? I know I learned it from you but how do you find resources to learn things like this.
Some apps like Next have documentation that is extremely insightful but nowhere in the React docs would I have learned how react actually works.

Just Great!

Many newer developers are running in development. Local host and all that, personally I have made a call to local storage in dev mode, and the program works fine. Will that not work in production?

jesus christ... I finally understand

i watched this video when it first came out and again last night. got much more out of it after getting my hands dirty with Next
great video

Would've been nice if you had explained how Nextjs works like with bundle splitting etc.

This is absolutely important background-knowledge! Fantastic explanation! Thank you! 😀👍

I'm confused - I've been following along with your T3 Stack Tutorial (I'm up to the part where we show user details in each tweet) and the page is definitely hydrating on load, the initial HTML is just a skeleton... Which seems to contradict what this video is saying?

You missed an important thing. Call of `getInitialProps` in _document.js file. Also <NextScript> <Main> etc are very important if you want to provide details on how REALLY works.

React = interactive sites

Next = HTML correct for sites as soon as they load

What about "how Next 13 ACTUALLY WORKS ?"

Why some people still use firestore on SSR? What are the benefits?

Valuable content, thank you

Amazing work, helped me fix small confusions

I had a hard laugh on "servers dont have windows because they run linux" :D excited about t3 stack

great explanation

lol they deprecated twitter card preview. fucking elon

Hey Theo, video on upgrading T3 app to use the app directory update of nextjs next? Why? Just because!

bro had a 28 minute slow motion meltdown culminating in him telling everyone to leave him alone. gg indeed. didnt even have to look up this dudes linked in profile up to know hes an engineer in san francisco 😂😂😂

I REALLY need a perfect SEO. I have just dumped NuxtJs which was terrible and I am in love with NextJS. Even tho it will take me a couple of months to rewrite I already see it will be smoother overall.

Thanks for sharing, you have mentioned that when browser requests to next server, next will execute getServerSideProps and then react will use those props. However, we can use getStaticPaths function to serve all dynamic routes pre-rendered HTML in built time. In that case, when a user requests to next server, will next server execute some react or just sending the pre-rendered HTML in built time instead of runtime?

Hi everyone, am I missing a part, or is this video simply explaining that NextJS will take care of the server-side processing through getServerSideProps and return the rendered HTML as a result.

After the HTML has been returned to the client, the next part is entirely in react.

I am still trying to wrap my mind about what happens when page contains components that can not be rendered on server, how does all that gets stitched up. I guess at best there would be holes, or place holders for client side to fill in?

I guess I would say "incomplete" rather than "incorrect" for the initial html.

Next can't do all of the things that can be in "this is next". The server could serve the original page with some parts that are based on cookies, etc.

You explained it so easily. Thanks for the effort.

I shared this with my co op student! Can you make the same for Astro?

That is a beautiful explanation, thank you, Theo!

You dropped this video at the perfect time! My team is starting a new application and we're considering nextjs and this was an awesome introduction :)