Next.js 15 Ruins Caching Even More

📚 Materials/References:

🌎 Find Me Here:

⏱️ Timestamps:

00:00 - Introduction
00:27 - Sponsor
03:30 - How Things Currently Work
05:21 - Production Mode Breaks Things
08:02 - How To Fix This

[zelli]

What we need in next js 15 caching wise:
-no cache by default
-not having to add "force-dynamic"
-same behavior in dev vs production

[incrypted]

Having different caching behavior for dev vs production is legit psychotic. I have never had as frustrating an experience learning to use a new tool as I did with Next.js. It's like you are destined to run into esoteric problems either caused by shitty, unclear documentation or a total lack of documentation. Unless, of course, you get lucky with your google searching and find the answer on some github issue from a year ago.

[Ivan-wmgm]

Another reason for me to switch to react-router v7, man next.js is a bunch of temporary solutions and weird work around every new release

[TheMindfulCraftsman]

Hi Kyle, I think you nailed it in this video. After 25 yrs of programming I never got the built-in caching strategy of Next. It is also best practice in virtually all environments to cache purely for optimization reasons and never as default bevavior. Hope the Next.js team reconsiders and requires opt-in for *all* types of caching in RC 15.

[dcd_music]

You definitely are one of the people who understand how Nextjs caching mechanisms work. Your explanation is waaay better than that of the vercel team, hands down! I struggled a lot trying to remove all of the caching on version 14.
Awesome channel!

[-Will-]

I have a lot of love for Vue SSR behind a Varnish cache. Simple to code in and simple setup.

[luffythestrchykid]

New version of NEXT JS basically means update yourself and climb a cliff and then expect most of the things to break .ie. jump of that cliff

[TheOnceAndFutureDoug]

Looking forward to the inevitable upcoming video on Next 15 caching strategies. :D

[atimney]

I agree this is confusing, but the example is contrived, if your doing crud then you will need to invalidate the path which will be obvious when your working with it, also if you need specific catch scenarios your going to think about these, but agreed this will catch out some developers. Keep up the good work man

[chriskennedy]

fucking front end is a mess. So glad I rarely develop in React, and mostly work on the backend outside of metaframeworks and focused on DICOM. In this role I now manage to completely avoid this shitshow, I honestly feel bad for you guys for having to suck this up.

I miss when the debate was as simple as being about lifecycle methods and whatnot. This is wild.

[하경-ez]

Thanks u kyle
I was facing this problem and I finally found the answer through your video 😊
God bless u man🎉

[qwerty-oryg]

Honestly, I've just stopped using next a while ago, been working with angular in my day job and now I'm just using it for all of my side projects as well. So much more enjoyable to code and no need to deal with all that mess next.js provides

[siya.abc]

I'm going back to Nuxt and Vue. It's stable now. This relationship with react and next is too toxic now.

[codinginflow]

I actually liked the default client-side router cache. It made navigation within the app very fast. But I guess you can't please everyone.

[AK-ijqf]

Goddamn everyday I become a little closer to migrating my entire month-old project to vite React + React Router instead of this cesspool

[sean]

As a react developer wanting to learn NextJS, this problem with 14 made me scrap the whole thing and switch back to regular react in my latest project. Might try again with NextJS 15 now that I understand the behavior from your video!

[georgemwaniki]

With next js Frontend development is becaming rocket science, I miss Nuxt 😢

[CodeXBro]

Next week's updates: Launching Next.js 16 fixing another something about caching and forgetting about a broken v14 and v15. Honestly, I have been struggling so much with weird issues in Next.js and unable to move fast in developing one of my side projects that's not even complex. I tried hard to do it in Next.js because the React team is pushing it towards it and I am comfortable writing React code. But I am starting to think of either moving to another framework like Remix or Nuxt or go React + Vite route.

[golden_smiles]

Front end in general is OK. Just don't lock to the shitty hypie technologies to get to the point when they go even shittier. It was a lot of signals about this situation before on NextJS.

[EinChris]

I'm old... I am still stuck with php for my personal page.
It works like it did 20 years ago. Almost the same code, but now on php 8.
For professional work, fortunately, I do not have to do web stuff very often.
But that looks so f-ed up. Is this really state of the art?
I thought writing cgis with perl was terrible. But that is even worse.
Where is the benefit from that? What is the advantage? It all looks so crappy.