I've watched numerous videos on Next.js 15, but yours stands out as the best! The way you explained everything with such simplicity and practical examples made it much easier to follow. Thank you!
The instrumentation change is not something to be skipped over. It brings things like OpenTelemetry into the next ecosystem. Things like this are huge for monitoring apps that talk across multiple services. Eg tracking from next to a graphql server to a REST api and back
Too many changes, too often, too many backward-incompatible changes... Next.js is becoming a framework for TH-cam content creators who get new material for their next video out of it. Companies building large systems and serious applications are slowly starting to avoid Next.js...
Indeed, you can literally see some websites (some major websites too) not upgrading to the latest versions, they stay on Next 13 I was a Next.js user since v9, but I started to give up since v13 and it's not the v15 that will make me comeback
Thank you very much! It's not obvious that you put so much effort into the video, it's nice to have people like you who make the hard work easy for us. Thank you!
At 04:58, I don't think that is the case anymore, I tried fetch with no option and it gave me a static page, but with the option cache:'no-store', which is supposedly the default, the page became dynamic.
Am i the only one who hates the heavy push for server side frameworks? I like my websites to have a loading spinner, and then present a fully working page to the user with smooth experience, while server side frameworks have unpredictable behavior and jittery experience just because developers feel the need to overcomplicate things. Isnt this one of the reasons that chatgpt website moved away from nextjs to a different framework Not to mention keeping seperate files for server and client makes perfect sense, while nextjs throws everything in one src file
Me too, i keep wondering why these moves all sudden all people talk about ssr. Thats why i cant wait for tanstack start. It’s the only meta framework with a mindset of client first, then if you need ssr you can opt-in. In one of my app, i need the capability to server render one page. No way i would use nextjs for that lol.
amazing video. Coming back to nextjs after a year and this explained all changes very well. Not sure how I feel about params being promises, but no more caching is amazing. P.S. Sorry but is this really the best haircut you can get?
It won't be a full new course. Most of Nextjs 14 is the same in Nextjs 15. I am planning to update any out of date videos and add new videos for new concepts but otherwise most of the content will stay the same.
I work in projects with lots of routes and components. Inherited React and Angular projects sucks. It 's practically impossible to upgrade the core frameworks because of breaking changes and tight coupling with TS. I started to to use Vue 2.6 with pure JS ( no TS ) in 2019 and practically was a minor work to jump from vue-cli to Vite and VUE 3. Old components are still in options api, while the new ones in composition api, all living together in peace. Don't need for SSR, so we make SPAs with dynnamic components. All starts quick and chunks loads when needed.
Of all these ssr framework, only tanstack start make me interested, probably because i love tanstack router (and tanstack query lol). Need to wait for version 1
@@qwerty-or1yg I just use React and Express - no server side rendering. Basically the MERN stack with my own frameworks and standards for writing code developed over many years.
Its really nice if you have filter form on homepage that redirects to list of products to use Form. My question is if I am at product list page and I have same filters form, do I just reuse that form since filters are the same ( it does not redirect but dynamically updates with new filters and new query params) ?
I have tried to upgrade the next js 15 using cli tools mentioned in docs, but I am continuously facing some error in react 19 RC version and also adding new Shadcn ui. Can anyone help me, how can I fix this ?
Is not internatilazation build in nextjs v.15? can you expain how it works please. what i understan we do not need to import an external library anymore and it working in other way?
I've gotten tired with Next.js. The rules are very confusing and they keep making breaking changes. You also need to write a lot of boilerplate just to create a component. I think it's better to move to Angular and Vue. Enterprises and startups like them, there's aren't much breaking changes, and better developer experience.
Still not recommend to update from 14 to 15 there is many dependencies not supported in nextjs15 due to React19rc since React19rc is not yet quite stable also some dependencies repository not yet applied it to support
be careful with the turbo flag i have problems with it developing api. i get errors I don't get when using next dev without it. not so experienced with next js but i can make chaos in my opinion... :)
0:00 1. Next.js 15 Launch 🚀 Introduction to the launch of Next.js 15 with new features 0:12 2. Release Candidate 2 Fiasco 🤦 Story about the unexpected release of Next.js 15 RC2 0:40 3. JavaScript Changes Journey 🔄 The challenges of keeping up with rapid JavaScript changes 0:56 4. Fresh Install of Next.js 15 💻 Overview of a fresh Next.js 15 installation 1:18 5. Code Mod for Upgrade 🛠 Exploring the code mod for upgrading from Next.js 14 to 15 1:48 6. Breaking Change: Async Requests 🔄 Explanation of the breaking change related to async request APIs 3:01 7. Minor Parameter Changes 🔄 Discussion on the asynchronous parameters and search params 3:49 8. Asynchronous Function Handling 💻 Handling asynchronous functions and promises 4:23 9. Improved Caching Mechanism 🔄 Enhancements in caching functionality for better performance 5:59 10. Enhanced Client Router 🌐 Improvements in client-side routing and caching 7:02 11. Upgrade to React 19 ⚛ Utilizing the latest version of React for enhanced features 7:14 12. React 19 Compatibility Using beta features of React 19 with Next.js 7:35 13. Improved Hydration Error Visibility Enhanced visibility of hydration errors in source code 8:05 14. Turbo Pack Support Introduction of Turbo Pack for faster compilation 8:59 15. Static Route Indicator Indicator for static pages to aid debugging 9:38 16. Unstable After Feature Experimental feature for running code after client request 10:29 17. Enabling After Function Learn how to use the unstable after function for post-rendering tasks. 10:57 18. Form Component in Next.js Explore the specific use case of the form component for page redirection. 13:09 19. Next.js Config Updates Discover the TypeScript support and self-hosting improvements in Next.js configuration. 13:48 20. Public API Security 🔒 Discussing the importance of securing server actions to prevent unauthorized access. 14:16 21. Secure Action IDs 🆔 Exploring the implementation of secure action IDs to enhance the security of server actions. 14:58 22. Action ID Usage 🔄 Examining the unique action IDs and their role in preventing abuse of public APIs. 15:50 23. Security vs. Obscurity 🛡 Highlighting the misconception of relying solely on obscurity for security measures. 16:19 24. Optimization for Speed ⚡ Overview of an optimization feature to enhance application cold start speed. 16:27 25. ESLint 9 Support 🛠 Introducing support for ESLint 9 and the end of life for ESLint 8 in Next.js 15. 17:12 26. Improvement 🚀 Enhancements in ENV file handling and version control. 17:41 27. Mastering Next.js 15 🎓 Recommendation for a comprehensive Next.js 15 course. 18:06 28. Conclusion 🌟 Gratitude to viewers and course link in description. Generated with Tubelator AI Chrome Extension!
Too many changes, too often, too many backward incompatible changes. I feel remix is better than next.js. Atleast it has very few and stable updates. I'll learn remix.
I steal have problem with caching in dev and production mode, this is terrible and dangerous! THE RESULT IS NOT THE SAME!!!! FCKKKKK I WILL GO BACK TO REACT, OMG!
what do you mean you dont know why they waited so long to release it? cause announcement is coming... But funny thing is its not stable as they got around 3,000 issues pending LOL... tried using it in a bigger project, but its still unusable.
I saw few of your videos and l kind of liked it but I don't understand why you Rap in your Videos.?? You speak so fast as you are in real hurry. Not everyone is native or habitual of the accent, so please keep that in mind.
I much prefer TH-cam channels like Fireship that don't subject their viewers to a permanent talking head hiding all the content. I find it very distracting and unnecessary. The audio should be enough especially for channels that mostly show text and code. Another annoying trend is showing unnecessary meme images and videos.
I've watched numerous videos on Next.js 15, but yours stands out as the best! The way you explained everything with such simplicity and practical examples made it much easier to follow. Thank you!
My guess is that Nextjs 15 was ready for months but they no longer wanted to wait for official React 19
A lot of changes were fixing current bugs and changing the caching system
I really appreciate the consistent quality of your content, and I appreciate all your effort on this!
You know how good of a teacher you gotta be to purposely make a mistake (at 11:51) to teach and demonstrate? Top tier
The instrumentation change is not something to be skipped over. It brings things like OpenTelemetry into the next ecosystem. Things like this are huge for monitoring apps that talk across multiple services. Eg tracking from next to a graphql server to a REST api and back
Exactly
Too many changes, too often, too many backward-incompatible changes... Next.js is becoming a framework for TH-cam content creators who get new material for their next video out of it. Companies building large systems and serious applications are slowly starting to avoid Next.js...
Then just dont upgrade
That's true for my company too hahah
True, don't make sense to learn this stuff, is waste of time
Next.js is horrible. Use Remix
Indeed, you can literally see some websites (some major websites too) not upgrading to the latest versions, they stay on Next 13
I was a Next.js user since v9, but I started to give up since v13 and it's not the v15 that will make me comeback
Thank you very much! It's not obvious that you put so much effort into the video, it's nice to have people like you who make the hard work easy for us. Thank you!
aitutorialmaker AI fixes this. Next.js 15 introduced major changes.
Always on point, Kyle! Thank you, I get up-to-date thanks to you!
We would like to see you playing that guitar 😊
Yes please!!! 🙏
on 2 mil subscribers
"we" is like 50 people.
My guys is extra consistent nowadays
Thanks Kyle for the NextJs 15 breakdown
As a newcomer to nextjs, the previous caching decisions they made were bonkers to me. I'm so glad they fixed it.
Flutter Dev here: I love Next ❤
Thanks for clearing everything, man ❤
Thanks, I didn't want to watch the whole conference, this is to the point and a good summary
After seeing so many updates & improvements I am one of very few devs who will prefer pages router over app router or remix
thanks Kyle love your videos man, this was really helpful.
Thanks for the great overview.
Nice and simple video. Thanks for the content!
great coverage! thanks for rerecording
Thanks for the awesome video! Do you have any plans to cover the new ESLint 9? Would love to see it!
At 04:58, I don't think that is the case anymore, I tried fetch with no option and it gave me a static page, but with the option cache:'no-store', which is supposedly the default, the page became dynamic.
Am i the only one who hates the heavy push for server side frameworks? I like my websites to have a loading spinner, and then present a fully working page to the user with smooth experience, while server side frameworks have unpredictable behavior and jittery experience just because developers feel the need to overcomplicate things. Isnt this one of the reasons that chatgpt website moved away from nextjs to a different framework
Not to mention keeping seperate files for server and client makes perfect sense, while nextjs throws everything in one src file
Me too, i keep wondering why these moves all sudden all people talk about ssr. Thats why i cant wait for tanstack start. It’s the only meta framework with a mindset of client first, then if you need ssr you can opt-in. In one of my app, i need the capability to server render one page. No way i would use nextjs for that lol.
seems predictable to me? and yeah, website performance matters.
3:53 just wanted to say thanks man I was building a new project and this error came up then I remembered your video you saved my days of hard work
your 0 users project?
@EDS432 yes
amazing video. Coming back to nextjs after a year and this explained all changes very well.
Not sure how I feel about params being promises, but no more caching is amazing.
P.S. Sorry but is this really the best haircut you can get?
Currently watching your next js course seems like I'll wait for the New one 😅
It won't be a full new course. Most of Nextjs 14 is the same in Nextjs 15. I am planning to update any out of date videos and add new videos for new concepts but otherwise most of the content will stay the same.
I work in projects with lots of routes and components.
Inherited React and Angular projects sucks. It 's practically impossible to upgrade the core frameworks because of breaking changes and tight coupling with TS.
I started to to use Vue 2.6 with pure JS ( no TS ) in 2019 and practically was a minor work to jump from vue-cli to Vite and VUE 3. Old components are still in options api, while the new ones in composition api, all living together in peace.
Don't need for SSR, so we make SPAs with dynnamic components. All starts quick and chunks loads when needed.
Can you do a vid please on the new “use cache” directive?
Of all these ssr framework, only tanstack start make me interested, probably because i love tanstack router (and tanstack query lol). Need to wait for version 1
Thanks a lot!
first thanks a lot for this useful video , what is your vscode icon theme bro??
Thanks for the video, do you have any video that talks about how to use next.js + turborepo + prisma to translate the above into English?
Everything I need to know? In 18 minutes? I hope you're right!
Was never a fan of NEXT and really only watched this to find out why I still don't want to use it.
what do you use instead? I've been using angular for years and I'm loving it. Anything you'd recommend I'd use instead of nextjs?
@@qwerty-or1yg I just use React and Express - no server side rendering. Basically the MERN stack with my own frameworks and standards for writing code developed over many years.
What an hot mess of beta, release candidates and dirty fixes. Am I expected to use this for work?
it was amazing!
Its really nice if you have filter form on homepage that redirects to list of products to use Form. My question is if I am at product list page and I have same filters form, do I just reuse that form since filters are the same ( it does not redirect but dynamically updates with new filters and new query params) ?
Oh so now we need to have all pages using asynchronous pages
14:37 if we can intercept server action vis midilware
beautiful 👀❤️❤️❤️ ... that said let start listening him😂😂😂
I'm just getting used to 14..
Next js 15 excited to use it🤩
a few more adds would be great
Interesting, I would expect Biome to be an option instead of just ESLint 9… but I guess is like pnpm, will take time…
Joined by recommendation.
I have tried to upgrade the next js 15 using cli tools mentioned in docs, but I am continuously facing some error in react 19 RC version and also adding new Shadcn ui. Can anyone help me, how can I fix this ?
Does downgrading version work?
Yeah I had the same. Just just 14.2 and wait for everything to settle down.
@@YakovFn yes then only it works
@@clamr6122 yeah hope so, and don't even anyone talking about it.
@@rahuldas_2004--legacy-peer-deeps when installing anything
Is not internatilazation build in nextjs v.15?
can you expain how it works please.
what i understan we do not need to import an external library anymore and it working in other way?
thanks
I guess I will be in next 14 for a while and upgrade to next when the stable react 19 is supported.
react@19.rc is stable; there is this only suspense thing that they are holding onto.
@@whoman7930and that's a big thing ! Everything else has been ready for a long time anyway
Should I just print "await" on every line of a Next.js-based project?
Yes, you should. That's what Next.js is famous for. Force you into some horrible ideas and decrease your productivity.
Hey Kyle, in India most of the Next.js Applications uses Next.js v12 or 13 so, why should one need to learn new versions ?
It's not true..I am using Next14
@gurpreetsingh6785 Are you currently working in a company ? If so then let me know if there are any openings for a Front-End Developer.
not really important but what icons do you use
can anyone guide me what to use? Next or Remix? I am new to both
I've gotten tired with Next.js. The rules are very confusing and they keep making breaking changes. You also need to write a lot of boilerplate just to create a component. I think it's better to move to Angular and Vue. Enterprises and startups like them, there's aren't much breaking changes, and better developer experience.
Yeah man, it's getting ridiculous.
Use Remix then
Yeah remix is still very good
I was about to agree with you until I read "Angular" 🙈
@@alexandreannic3370 Angular is used in most enterprises. Whether you like it or not it's the most preferred option for the big guys.
Bro is real life Reed Richard's 😅
😂
❤❤❤
It borke backwards computability for lot of library
Still not recommend to update from 14 to 15 there is many dependencies not supported in nextjs15 due to React19rc since React19rc is not yet quite stable also some dependencies repository not yet applied it to support
Just add --legacy-peer-deps while installing the dependency
It should work
@@Ouyiggh8807 it cause mui Hydration if you using mui
@@Ouyiggh8807 yeah you can use --legacy-peer-deps but you can't skip of hydration error specially if you use MUI
Good features, but not really a "wow" for me
It looks like I'll keep using 14.2.7 for a while longer...
same but i'm keeping version 12 lol. just saw their new caching improvement in their blog and i'll wait until v16.
When nextjs have better middleware and Request handlers, let me know
Nextjs is still for building basic websites
will people already bought thr course would also get the updates?
be careful with the turbo flag i have problems with it developing api. i get errors I don't get when using next dev without it. not so experienced with next js but i can make chaos in my opinion... :)
Anyone facing issues with MUI after upgrading to next-15 and react-19?
Google Font use techniques also changed anyone give one example .
I'm done with NextJS
Best!
0:00 1. Next.js 15 Launch 🚀
Introduction to the launch of Next.js 15 with new features
0:12 2. Release Candidate 2 Fiasco 🤦
Story about the unexpected release of Next.js 15 RC2
0:40 3. JavaScript Changes Journey 🔄
The challenges of keeping up with rapid JavaScript changes
0:56 4. Fresh Install of Next.js 15 💻
Overview of a fresh Next.js 15 installation
1:18 5. Code Mod for Upgrade 🛠
Exploring the code mod for upgrading from Next.js 14 to 15
1:48 6. Breaking Change: Async Requests 🔄
Explanation of the breaking change related to async request APIs
3:01 7. Minor Parameter Changes 🔄
Discussion on the asynchronous parameters and search params
3:49 8. Asynchronous Function Handling 💻
Handling asynchronous functions and promises
4:23 9. Improved Caching Mechanism 🔄
Enhancements in caching functionality for better performance
5:59 10. Enhanced Client Router 🌐
Improvements in client-side routing and caching
7:02 11. Upgrade to React 19 ⚛
Utilizing the latest version of React for enhanced features
7:14 12. React 19 Compatibility
Using beta features of React 19 with Next.js
7:35 13. Improved Hydration Error Visibility
Enhanced visibility of hydration errors in source code
8:05 14. Turbo Pack Support
Introduction of Turbo Pack for faster compilation
8:59 15. Static Route Indicator
Indicator for static pages to aid debugging
9:38 16. Unstable After Feature
Experimental feature for running code after client request
10:29 17. Enabling After Function
Learn how to use the unstable after function for post-rendering tasks.
10:57 18. Form Component in Next.js
Explore the specific use case of the form component for page redirection.
13:09 19. Next.js Config Updates
Discover the TypeScript support and self-hosting improvements in Next.js configuration.
13:48 20. Public API Security 🔒
Discussing the importance of securing server actions to prevent unauthorized access.
14:16 21. Secure Action IDs 🆔
Exploring the implementation of secure action IDs to enhance the security of server actions.
14:58 22. Action ID Usage 🔄
Examining the unique action IDs and their role in preventing abuse of public APIs.
15:50 23. Security vs. Obscurity 🛡
Highlighting the misconception of relying solely on obscurity for security measures.
16:19 24. Optimization for Speed ⚡
Overview of an optimization feature to enhance application cold start speed.
16:27 25. ESLint 9 Support 🛠
Introducing support for ESLint 9 and the end of life for ESLint 8 in Next.js 15.
17:12 26. Improvement 🚀
Enhancements in ENV file handling and version control.
17:41 27. Mastering Next.js 15 🎓
Recommendation for a comprehensive Next.js 15 course.
18:06 28. Conclusion 🌟
Gratitude to viewers and course link in description.
Generated with Tubelator AI Chrome Extension!
Bro is looking older lol, been a subscriber for 5+ y now ..
Too many changes, too often, too many backward incompatible changes.
I feel remix is better than next.js. Atleast it has very few and stable updates. I'll learn remix.
NextJS became PHP as I know it from my very early career... Blee
I just want to drop a comment that says `I'm a Full stack developer thanks to you 🌹`
I'm glad I could help but it was your hard work that got you to where you are.
I steal have problem with caching in dev and production mode, this is terrible and dangerous!
THE RESULT IS NOT THE SAME!!!!
FCKKKKK I WILL GO BACK TO REACT, OMG!
Next auth, Mongodb, stripe don't work on it no more.
Is it true, i use those please provide a source for the article, let me check
what do you mean you dont know why they waited so long to release it? cause announcement is coming... But funny thing is its not stable as they got around 3,000 issues pending LOL... tried using it in a bigger project, but its still unusable.
i have given up on js
lol pussy
Say no to next js❎ only pure js ✅
Shake shake
man why u all time shaking your head 😅
I saw few of your videos and l kind of liked it but I don't understand why you Rap in your Videos.?? You speak so fast as you are in real hurry. Not everyone is native or habitual of the accent, so please keep that in mind.
First comment ❤
first !
The truth is using Nextjs is really annoying with server side and client side stuff, awww
so much change, if project existed you should not upgraded it 😢
Can I ask you a question please
No
man why do you shake your head like you are sick ?
Listen up Tate brothers !!!! 💪💪💪
kyle you take up too much space in the video...
Yeah, no thanks.
I much prefer TH-cam channels like Fireship that don't subject their viewers to a permanent talking head hiding all the content. I find it very distracting and unnecessary. The audio should be enough especially for channels that mostly show text and code.
Another annoying trend is showing unnecessary meme images and videos.
Google shows a commercial every 15 seconds
I am using next 69
noice 🤣