Next.js 15 RC 2: Explained!

[@renovantm125]

Thank you for bringing entreprise ready tools like Next.js and Vercel. It is not for every project for sure. But for a SaaS project it’s Perfect!

[@LutherDePapier]

I'm really liking all of this super experimental stuff. 🍽

[@devdatkumar4970]

Is it possible to place a small (blue or another colored) dot in the Canary documentation next to tabs to indicate specific changes, rather than having to check each tab individually for updates?

[@omidsoleimani3817]

I totally agree with this suggestion. I'm also struggling with the same problem, and it's quite time-consuming to constantly check the entire documentation to find what’s new or updated. A small colored dot or badge next to the updated tabs would be a huge help in keeping track of changes more efficiently.

[@leerob]

@@omidsoleimani3817 Rather than checking the docs on a per file basis, I would recommend starting from the blog posts where we talk about what has changed in the v15 release, and it has links back to the docs for those sections!

[@LutherDePapier]

Got it, middleware is where I can tell if somebody is authenticated or not in order to redirect to login if they aren't, but full database-driven authentication has to be done at the page level itself.

[@leerob]

Correct! Similar with authorization, you would want to check if the user has access to delete an item, for example, at the server action level. I have an example of my GitHub under next-saas-starter.

[@SourceHades]

That's so stupid, Next.js is getting worse and worse with each version

[@parkerrex]

great update!

[@王尼玛-g9z]

Very good, you indeed need to improve the cache management mechanism, which is often the root of chaos

[@phantom7132]

Thanks! I hope the performance issues during development with dynamic routes get fixed…

[@StephenRayner]

Nice work Lee 👌

[@Sandurz]

I'm struggling to invent any scenarios that get a latency win from the async request APIs change, especially with how it might relate to PPR. Do you have any sync vs async examples you could share that would bring some clarity to what situations and patterns will benefit from this?

[@succatash]

So then we know nextjs 16 RC 3 comes out at next conf?

[@aymenbachiri-yh2hd]

thank you so much

[@morphexyt]

i have a general question about async server components and caching in next js v14 app router, if i have a dynamic route that has an async child component that fetches its own data and that data is cached using unstable_cache and that child component is wrapped within suspense , my issue here is when the parent component of that child async component is an async component itself too , the fallback for the child component suspense will always show no matter if the child's data is cached or not , but if the parent isnt an async component the fallback will only show while the data is still being fetched as expected and upcoming request will return the cached data w/o the fallback first ( im taking about hard navigations / initial html returned from the server)

[@HansOttoWirtz]

The link in the description still refers to the blogpost from May

[@leerob]

Thank you, fixed!

[@kasper369]

This is amazing,

[@timelod]

How can I get type-safety when exporting configs like you (59:17)

[@leerob]

If you are using VS Code, ensure you're using the Next.js TS Plugin nextjs.org/docs/app/building-your-application/configuring/typescript#typescript-plugin

[@timelod]

@@lukesrw amazing, thanks

[@Michael-Martell]

Hopefully the memory leak from es-lint gets resolved

[@Vantivify]

Any links to that ?

[@ilovemacross]

use biome js?

[@sergiigulaga1486]

What about loading.tsx and not-found.tsx when you using both. Is it still return status 200 when the page is not found?

[@nobir98]

Deno 2.0 has been released, and they claim that NextJS is supported. Is there any codemon that will be released in the future so that full production-ready Nextjs can be run on Deno 2.0?

[@Farruh_13]

So when next 15 gonna be stable and production ready ?

[@dashed9958]

I think it'll be this week at the nextjs conf

[@Farruh_13]

@@dashed9958 Yeah, i thought so, but i don't get it, why they've released new beta version, if there coming stable version

[@cinipedia]

I just finished learning 14 and here comes 15 ! Is it worth learning JavaScript as new package drops are happening too often !

[@tutkuns]

Can someone tell me if I can use different alphabets (arabic, cyrillic, etc.) in the `products` and `product-1` url structure on my `products/product-1` pages? If it is available, where would be the best way to do this?

[@leerob]

You could use dynamic routes for the parts you want to localize.

[@SaurabhSrivastava-i1q]

What does NextJS cannot do for which we might require NestJS? Need some solid reasons for scalable apps.

[@boy291-z8c]

You can't do long running stuff with nextjs, so think stuff like websockets. You can't use nextjs as a websocket server unless you setup a custom nextjs server which in itself opts you out of some of the nextjs features. The way nextjs implements the concept of a middleware (by asking you to use a middleware.js file which can't even do network calls) is horrible imo, but with nestjs, middlewares are well architected. If all the backend of your app does is to CRUD a database and send the result back to the frontend, then sure, nextjs is fine for that, but if you need to do more complex stuff on your backend like setup complex auth roles, do long running jobs, etc, then nestjs is better suited for those. Ultimately, I think nextjs is a frontend framework trying to do backend stuff while nestjs is a full-fledged backend framework.

[@SaurabhSrivastava-i1q]

@@boy291-z8c Thanks a lot man. I am setting up a monorepo with pnpm using nextjs and nestjs and tRPC instead.

[@LutherDePapier]

I think there's a better way to ensure server actions are secure, but so far don't quote me on this: making server actions inline and passing them as props. I looked into .next just like you did and I don't think I've seen any similar reference to any of my inline actions. My theory is that inline actions are created with the server components they belong to, and therefore they don't even exist if that component does not exist, making them ephemeral endpoints that live and die with that server component, kinda like Revolut's single use cards imo. You can even hook to these actions the user you've already authentified on server component, so that the action doesn't not need to do authentication and only needs to do authorization before it proceeds, again, based on the user that the server component of the action has already verified.

[@nivethan_me]

seems like Next 15 is not going to release on Nextjs conf 2024. is it because React team takes some time to improve React 19?

[@jsvrs]

I also want "use serverless server"

[@lemontec]

feels like they had hoped for a faster release of React 19 and this would have been 15.1

[@koby9340]

Im still learning next 13 fgs 😭😭

[@diegosk8bt]

damn, too many considerations when building with nextjs. is it the same with others similar frameworks? remix/nuxt/etc..

[@lamhung4899]

Fortunately, No 😂

[@TheMindfulCraftsman]

Great video, but unfortunately we have been thinking for a while now about ditching Next.js after many loyal years because of what you explained in minute 59. The thing is, if a framework behaves differently in dev and production, be it due to unwarranted caching, "optimizations" noone explicitely asked for or hidden config settings, it is unusable in practice. I cannot keep explaining new Next.js features to our juniors every couple months when such basic assumptions like getting the current time on a page refresh are not reliable in production and need a hidden setting as a workaround. Testing has become already cumbersome due to different dev/staging/prod behavior. Caching, optimizations, the large amount of required async calls (which is source of error no. 1 in practice!) etc. should *always* be opt-in by default. The layered optimization process can follow if needed and explicitly asked for. I'm afraid the hunt of the team to over-optimize areas and defaulting to that might hurt this great framework badly.

[@leerob]

Data caching is opt-in by default in v15. A bit more on where we're headed here: nextjs.org/blog/our-journey-with-caching

[@OnlyJavascript]

endless breaking changes and it kills our time.

[@leerob]

Did you try the codemod? Should require a very small amount of time (for hopefully a good benefit 😁)

[@LuxAeterna93]

it's not endless breaking changes, in a major version update, breaking changes happen. And yes the computer world is always evolving till the end of time.

[@muneebakram1670]

Next.js (React in general) is getting overly complicated and diverging from the original purpose they were created for. for me I haven't started using next 14 because It just adds a lot of complexity rather than adding actual value.

[@serhanguney492]

Quite true. It feels like they pivoted from React to something else. I haven’t used 14 yet either and I really don’t want to have to

[@rifatrahman1417]

Its true that its complicated but when you start to use it will simplify your many works

[@nivethan_me]

React realized its mistakes and evolving with time. i make a outlook plugin(which using webpack) and the index.js file was whopping 18mb. as your app grows bigger and bigger you initial file will larger. and user needs to see a white screen until the download finished. now with server components you can render the initial page from server and provide a much better user experience

[@abdarker]

if it doesn't get complicated after few years job value will be 0

[@muneebakram1670]

@@nivethan_me These are very rare cases I believe only very little percentage of projects out there require this complex partial rendering , server side actions and all other fancy stuff but most of the projects don't need this kind of like Deno. they could have interduce a new meta framework to handle this. instead of making things more complex in coming years they will drop the sport for old version and everyone will be required to upgrade. but this is just my opinion.

[@ankitkumarjat9886]

Looks like Now it's time to ditch nextjs 😂😂😂

[@leerob]

Why is that?

[@ankitkumarjat9886]

@@leerob oh my god lee replied 😊 It's Because we are not getting a stable release. I just had a discussion at my work we are going for remixjs instead of nextjs for a new project because our manager is not happy with the stability of the nextjs 😭

[@ankitkumarjat9886]

@@leerob I am still hoping that stable release will come soon and at that time I can stand in the favour of nextjs

[@leerob]

@@ankitkumarjat9886 You can always start from the last stable release (in Next.js 14) - you don't have to start with a prerelease! We are planning to have a stable v15 release very very soon though, so might be a moot point.

[@ankitkumarjat9886]

@@leerob yes that is exactly what I said. It depends on the whole team, let's see what will be the final decision. Although this release looks great. I will be trying them this weekend. 👍