Next.js is a popular React framework that allows developers to build server-side rendered web applications with ease. The latest release, Next.js 15 RC 2, brings some exciting new features and improvements that make it easier than ever to create high-performance web applications. In this tutorial, we will explore the key changes in Next.js 15 RC 2 and take a closer look at how to get started with this release.
What’s New in Next.js 15 RC 2
Next.js 15 RC 2 comes with several new features and enhancements that improve the developer experience and performance of web applications. Some of the key changes in this release include:
-
Experimental support for React 18: Next.js 15 RC 2 includes experimental support for React 18, allowing developers to take advantage of the latest features and improvements in React.
-
Improved static site generation performance: Next.js 15 RC 2 introduces several optimizations that improve the performance of static site generation, making it faster and more efficient.
-
Improved TypeScript integration: Next.js 15 RC 2 includes improved TypeScript integration, making it easier for developers to write type-safe code in their Next.js applications.
-
New API for dynamic routes: Next.js 15 RC 2 introduces a new API for dynamic routes, making it easier to create dynamic routes in Next.js applications.
- Improved error handling: Next.js 15 RC 2 includes improved error handling, making it easier for developers to debug and troubleshoot issues in their Next.js applications.
Getting Started with Next.js 15 RC 2
To get started with Next.js 15 RC 2, follow these steps:
- Install Next.js: If you haven’t already installed Next.js, you can do so by running the following command:
npm install next@15.0.0-rc.2- Create a new Next.js project: To create a new Next.js project, run the following commands:
npx create-next-app@15.0.0-rc.2 my-next-app
cd my-next-app- Run the development server: To start the development server, run the following command:
npm run dev- Explore the new features: Once the development server is running, you can explore the new features and improvements in Next.js 15 RC 2. Try experimenting with dynamic routes, static site generation, TypeScript integration, and more.
Conclusion
Next.js 15 RC 2 is a major release that introduces several new features and improvements to the popular React framework. By taking advantage of the new features in this release, developers can create high-performance web applications with ease. If you haven’t already tried Next.js 15 RC 2, now is a great time to upgrade and explore the exciting new capabilities that it offers.
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?
great update!
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.
So when next 15 gonna be stable and production ready ?
thank you so much
I just finished learning 14 and here comes 15 ! Is it worth learning JavaScript as new package drops are happening too often !
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!
Thanks! I hope the performance issues during development with dynamic routes get fixed…
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?
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?
Im still learning next 13 fgs 😭😭
feels like they had hoped for a faster release of React 19 and this would have been 15.1
damn, too many considerations when building with nextjs. is it the same with others similar frameworks? remix/nuxt/etc..
I'm really liking all of this super experimental stuff. 🍽
The link in the description still refers to the blogpost from May
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.
Hi Leerob,
import { GoogleTagManager } from '@next/third-parties/google'
multiple scripts of RootLayout (e.g. analytics, etc)
reduce the performance drastically,
is there any solution or example ?
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?
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)
Looks like Now it's time to ditch nextjs 😂😂😂