How NextJS REALLY Works 

same

Yeah .. Im an SEO guy trying to explain how to deploy JS correctly ... this makes my work with engineering teams a lot easier ... thank you!

I was the same man, then I tried it and found out that it is actually kind of a wrapper around your React application which lets you render portions of it on the server. It can seem as a lot when you read or hear about it, but when you actually start building with it following the docs, it all makes sense and it's not nearly as complicated as I thought before. Having a kind of solid understanding of React helps though, you can then easily differentiate Next from React parts.

Thanks for sharing! I suddenly started seeing this as well recently on my sites and was wondering what broke lol

This is super good to know thank you

No?

It is an SPA. _app only mounts once and handles all page routing so _app is the single page. NextJs just handles it quite cleverly making everything seem less. But you are right, the title of the video was confusing since I was expecting a deep dive into how the framework was built.

@@rico454 What you said is true and yes I think the terms are usually juggled around. Although it looks like MDN defines a SPA as an application which loads a single document page and updates that document's body using javascript. You can look it up. AFAIK it's neither of those 2, it's a Hybrid react framework.

@@sidwebworks9871 Thats what i think of when I hear SPA as well. So I'm a bit confused still. If that's not how nextjs works, then its just a MPA, that becomes SPA after html is requested, why not just become a static page at this point ? Isn't being SPA the biggest selling point of... well single page applications ? Because it makes navigating through pages so much faster. But next loses that ability by requesting the server side rendered html at every route change. I feel so dumb for not understanding the point of nextjs but im also still a beginner

@@sidwebworks9871 Maybe I’m confused but doesn’t Next adhere to that criteria? _app is loaded once and everything else is loaded with javascript, whether it’s static or SSR? Well that’s how I assume it works, I might be wrong

Do you mean bringing client credentials, such as tokens, when the server component making requests?

I don't know what you mean but serious information or data should always come from a secured api. You shouldn't just hide sensitive information in your client side app but should also secure your backend. Always verify who the user is in your backend before you send that data to your frontend. Doesn't matter what you are using this shouldn't be problem.

The Twitter card preview has been disabled for everyone since April 2022.

@@SatyamSingh-rq2tc Amazing that they still have the website up then lol

you can SSR with Vite too

@@magne6049 thanks! I guess my question is more about where do tools like vite fit? Does it come down to the other specific feature they have other than SSR to determine whether I want to use (i.e.) vite vs nextjs? Sorry I may be just lacking knowledge about vite

Yes its its whole purpose

PHP and the likes do "classic server-rendered templates", but SSR is generally used to refer to rendering an SPA on the server. Using SSR for the former can be confusing, albeit semantically correct.