The Problem with Next.js

⭐ Become a full-stack web dev with Zero To Mastery Courses:

👇 Follow Me On Social Media:

(00:00) Intro
(00:08) Welcome
(00:53) Demonstrating the Problem
(02:59) Why the Problem Exists
(04:57) Also Applies to Route Handlers
(05:21) How to Opt-Out of the Default Behavior
(07:52) Final Thoughts

📚 Tutorial References:

#nextjs #problem #broken

[yanfoo]

Caching should be opt-in, not opt-out. Same thing for env variables which are consumed at build time. We have apps that read from remote configurations when they start, and this created issues because the config is also read at build time. Having static data is great! But the cache control in Next is quite frustrating.

[iPankBMW]

+ if you use soft navigation with <Link/> then it introduces even more "unexpected behaviour for the developer". There is still a 30 second cache you cannot opt out of, even with noStore()

[hossamawad]

I was just having a problem related to this topic and your video helped me grasp the concept behind it, leading me to properly understanding and fixing the problem, thanks 🤝

[TheBlueDude]

Only recently found your channel. Amazing tutorials. Thank you.

[dylanstephens]

Great video. I recently ran into this issue when using the T3 stack. T3 was throwing a DYNAMIC_SERVER_USEAGE error during builds and noStore() solved it. I'll be honest, I didn't understand why it worked, but it did.

[Movoid]

Thank you for the great explanation and sharing!

[_singledev]

Normally, the code works in the development phase, but gives an error in the production phase. The opposite happens in next.js.

[jakeunderland]

subscribed!! this is some great stuff Dave, thanks for sharing with us!

[roger_that_do_you_copy]

Can't explain better than this! Awesome video!

[killian]

Hi Dave! Your videos are absolutely amazing! I am currently digging into secure web protocols, I wonder if you can make a video of how to prevent or mitigate attack on a web application. Thank you.

[myview]

I have one question when we work in next js and node js then nodejs devloper send token in response then we can get it in client side then how we can protect page in middleware using server side because next js middleware run on server

[ogtgabriel]

i have noticed on nextjs14 when using react query on development on the first time i open the localhost the site has problems with loading the content incoming from react query, to fix i just refresh the page. Luckily on production this doesnt occur

[Santiego]

Do anyone know a next.js website that utilizes react server actions and has a crud type response time close to 100 or even 200ms? Would love to see it. Thanks.

[yukendhiran]

I'm getting wierd error that i can't track down, in dev mode is perfect but when I build at generating static page stage I'm getting errors, i started my project with bun when I try to run it with node getting module not supported use common js ...
I don't know wtf is happening I'm not building a server here, it's jamstack app and it's fully frontend

[georgemwaniki]

Thanks for covering this amazing content as always

[negativerfan]

What you are trying to say is: NextJs is broken. "It is by design" ~ yeah, by design bad. It is not like this is the only thing that sucks in nextjs.

[stanislavus]

this is what I call a quality content!

[allessioyassine]

Nice content as always. I just wanted to ask if your next JavaScript course, the one covering version 13, is still suitable considering the recent upgrade to version 14. thanks ^^

[yarapolana]

this is why I moved to Remix, you have way more freedom on how you want things to work.

[Michael-Martell]

Routing, both Links and programmatic. Also, if you wanna map an array, and return a conditional check on the array, before rendering, but you want to to wrap in an empty container for styling reasons, it needs a key… forcing you to use the div, breaking styling. Also there should be a way to optionally pass state from a layout to the pages that use the layout.