Next.js 15 RC 2: Explained!

[devdatkumar]

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?

[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?

[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.

[LutherDePapier]

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

[imorphex]

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)

[sergiigulaga]

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

[SaurabhSrivastava-iq]

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

[王尼玛-gz]

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

[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?

[Michael-Martell]

Hopefully the memory leak from es-lint gets resolved

[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.

[HansOttoWirtz]

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

[jsvrs]

I also want
"use serverless server"

[diegoskbt]

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

[tuber]

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

[lemontec]

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

[OnlyJavascript]

endless breaking changes and it kills our time.

[muneebakram]

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.

[ankitkumarjat]

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