Here’s a summary of the key points from the video with timestamps: ****00:00** - Introduction to Next.js 15** - Next.js 15 released just before Next Conf. - Major focus on making the framework easier to use, with much-needed changes. ****00:22** - Sponsor: Clerk** - Discussion on how Clerk simplifies authentication (SSO, multi-factor, passkeys). ****01:08** - Stable Release of Next.js 15** - Next.js 15 is stable and ready for production. - New `next@codemod` introduced to help update codebases automatically for async changes. ****01:35** - Breaking Changes (Async)** - Some breaking changes related to async behavior. - Example: Previously, calling `cookies` did not require `await`, but now it does. The codemod automates these updates. ****02:27** - Caching Defaults** - Caching behavior changes: `fetch`, `get` route handlers, and client routes are uncached by default. - Explicit caching must now be specified. - New caching options: `no-store`, `force-cache`, and `static`. ****03:45** - Page Components No Longer Cached by Default** - Page components are no longer cached by default, ensuring fresh data when navigating. ****05:07** - React 19 and Compatibility** - React 19 (RC) is used with Next.js 15. Pages Router remains compatible with React 18. - React Compiler is out of beta. ****06:22** - Next.js 15 Aligns with React 19** - Next.js aligns its release with React 19 to minimize future delays. - Backward compatibility with React 18 remains. ****07:32** - Pages Router Support Continues** - Pages Router will continue to be supported for new and existing projects. ****08:22** - React Compiler Eslint Plugin** - React team’s eslint rules were refined during the creation of the React Compiler. Recommended for all React apps. ****09:16** - Hydration Errors Improvement** - Hydration errors are now more informative, providing detailed diffs to identify issues. ****10:30** - Turbo Pack for Dev Mode** - Turbo Pack is the new default for faster development builds. It's not yet ready for production builds but will be soon. ****12:45** - Static Route Indicator** - New static route indicator helps developers understand which routes are static or dynamic during development. ****14:02** - `waitUntil` and `after` for Async Operations** - `waitUntil` and `after` help handle asynchronous background tasks more efficiently on platforms like Vercel. ****16:21** - Instrumentation.js for Error Management** - Introduction of `Instrumentation.js` to improve error tracking and logging, especially for platforms like Sentry. ****17:16** - Form Component** - The new form component supports prefetching and client-side navigation with progressive enhancement. ****18:39** - TypeScript Support for Next Config** - Next config files now support TypeScript, making it easier to see keys and experimental flags. ****19:56** - Sharp Package Included for Image Optimization** - Sharp is now included by default in Standalone output mode, simplifying image optimization. ****21:26** - Server Actions Security Drama Resolved** - Security concerns with server actions were addressed through encryption and randomized IDs. ****24:44** - Bundling of External Packages for Servers** - External packages are now bundled server-side to improve performance, particularly in serverless environments. ****26:04** - Server-Side Optimization** - Next.js now allows control over bundling external server-side dependencies for improved cold start times. ****27:47** - Improved Static Generation** - Static generation speed has been improved, and fetch cache sharing across multiple pages is now possible. ****29:28** - Concurrency Controls for Static Generation** - Advanced controls over static generation, including worker concurrency, are introduced to speed up resource-intensive tasks.
@@Joshua.Developer remix doesnt give you much fancy things, its route based data loading and route based actions just like a traditional server rendered app but most people just hear this and assume that you would have to just prop pass everything to components but tbh its a skill issue. Remix has some great hooks like useMatches for that problem and error boundaries are so great, you get to learn so much about the web like http caching and how easy it is to cache. For example, I implemented my own route cache that allows me to cache which ever route i want to, not like next js route cache that you cant change. Honestly, only things remix lacks is middleware and type safety in actions easily.
12:43 I like it! Tiny little thing, but so much value! You get to know if your page is static right away :D Also, you can see if page is static after build in console
clerk is doing evil shit with their pricing lately. you need to pay for their super premium tier in order to impersonate users - something which is tablestakes in other auth provdiers
@@Sub-05-19 Yapp agree, but sadly for my workload react is still preferred because of its extensive support in Web3 libraries and even other libraries.
Looks like I will have to wait some time to upgrade since framer-motion code breaks after upgrade. Won't even build. Complains that className is not valid anymore on motion elements. Might be a simple fix but I would rather not risk breaking the live env.
You need to update framer motion to v12 canary to fix that className type issue. Still not recommended to upgrade to Next v15 since React 19 stable isn’t out yet
does the Nextjs solve the router events problem for app router? in pages router, we had routeChangeStart, routeChangeComplete and routeChangeError which are crucial in pages that have forms and help to prompt users if they really want to leave the page without saving what ever they were doing. but this event were not available in app router. so is this feature available in nextjs15?
@@hello19286How did using an unstable version of React work out for Next in v14? I imagine it’s not quite that straight forward with re: FB and Instagram.
Thanks for this video! Would love to see a video that shows you upgrading a real project that uses ShadCn/UI. For me, it does not work at all as the radix-references fail. As a relatively new NextJS developer, this would be very helpful to see how to deal with "third party" packages when upgrading.
Thank god they are finally getting rid of their ridiculous caching by default BS. That was such a bad decision on their part. The other thing that annoyed and shocked me was when I was doing a build and it was trying to connect to my database. I was like WTF, why are you trying to access my DB at build time?
29:05 ...can someone help me how to zoom like this? is it some bind of recording software you are using (probably OBS?) or is it something i could achieve with basic macos screen recording?
Kinda funny that clerk is the sponsor because it's not fully ready for next 15 right now. They merged the PR for next 15 compat but haven't released it yet...
From a mere technical and un-opinionated pov it seems that for the most part they just fixed some "dumb" bugs or weird decisions/assumptions they have made in the last 14 versions... (14!!). I'm not blind: I can see why a lot of peoples are using Nextjs and why there is a lot of hype everytime they just "fix" something that in another stack regular devs will throw a pile of s...t against, but from a dev which is actively in the industry for 20 years sorry, but I still don't buy it (but this is just imho): when they release Next16 maybe they will point at all the mistakes done in Next15... However I recognized that is still a framework with a lot of features, especially for modern frontend (but I do not understand why not using Vite as default btw) when other "batteries included" solutions don't have such solid concepts (or at least into the core and maintained by core team members). Happy coding everyone!
I was so hyped about 13 and 14 but it really is painful. Especially the default caching in 14. Vercel made programming stupidly more complicated. If they want devs to experience the cool things of Server Components, Server Actions, then just implement it and hide from us. I'm switching to Remix and I hope they will do RSC better than Vercel's
@@mickomagallanes1185 Yeah I had the same progression of hype to refactor hell and eventually biting the bullet and bailing on Next. I really dont know why we're pushing SPA inspired javascript frameworks to the server. It's the worst of both worlds.
18:30 ok sure, but that is really not difficult code…. looks like every form data submission function I ever wrote back in vanilla JS and jQuery days 23:50 “weird concerns”? Really? This is one of the most popular react metaframeworks out there, with massive adoption by junior devs and total n00bs…huge target for malicious actors looking to affect a large number of sites with a single exploit. Nothing “weird” about such concerns.
Clerk is not ready for Next15, they rely on the sync version of headers(). Until they update Clerk to use the async version released with Next15 it won't be ready.
26:31 I have strugling with eslint for so long! Every project starts with configuring this mess. I both love it and hate it. Love for simplicity of adding rules. Hate for awful configuration and setup experince. Also in-IDE explanation of rules would make a huge difference! Each freaking rule need to go their site to read about - obnoxious!
This is like putting new tires in your car that the manufacturer didn't approve yet. It must be insane to install and use that package for now. Now try explaining to the Jr of your team why he can't depend on alpha/beta/rc now haha
😞🤧😤 I think that if Vercel/Nextjs develop consistent solutions thinking about the next generation of applications... it will be worth it for mid-big companies to pay for services that, in the end, will save them costs in other areas of infrastructure. Good for Vercel, good features
I read every comment in this thread. Most people are mad at nextJS and want to use remix (if they need react libraries) or svelte5 which just came out. Not many people in the comments are happy with how "messy" next.js is right now. Feels like we're the canaries in the coalmine
Maybe I’m in “enemy territory” here, but NextJS just feels like the continuation of “web dev is a hot mess”. Crappy dev tooling and DX. Is there a better framework for someone building SaaS apps and “not building facebook”?
We are building B2B SaaS Platform and it's currently based on NextJS (luckily without too much serverside stuff. Migrating right now to vite. Looks good 🌞 80kloc in size to have a reference. Will report.
@@theSnackableCTO I’ve seen another saas kit that use Bun. I just want a highly opinionated “fast launch” solution. I don’t care about customizing build or state solutions etc.
@@utubes720 maybe blitz.js or redwood.js. never used them myself. Bun ofc interesting. But maybe not yet evolved long-term. If that matters in this case :)
two months after theprimagen called out people using libraries like clerk to make projects instead of making something good, theo gets sponsored by clerk💀💀
@@nickwoodward819 tbh clerk has sponsored a lot of these tech people, I dont think I've seen a video where someone actually used clerk because it was better than alternatives, but its not the case. I dont like these type of tech to sponsor these many tech influencers, Snapdragon X elite is a great processor but on initial release it was so hard to find an independent review that it sort of makes me feel that I should not trust these sponsored reviews.
@@aberba try to deploy enterprise size next app outside vercel, and compare it. Also seek on RUclips there is a lot of technical content why deploying next.js app outside vercel is rubbish
@@coder_one how is enterprise deployment build different from regular VPS deployment build? Again you haven't mentioned a thing except there's some complaints on RUclips
@@maciekdeveloper There's a 'fill' prop, an 'objectFit' style, and if you need your image as background, you can do it with the 'getImageProps' function
@@maciekdeveloper There's the `objectFit` style, the `fill` prop, and if you want your image as background, you can do it with the `getImageProps` function. What else is missing?
There's the `objectFit` style, the `fill` prop, and if you want your image as background, you can do it with the `getImageProps` function. What else is missing?
Next is garbage. I am so grateful to be working for a company that uses vue. Next has been systematically destroying React. I can't begin to express how much I dislike Vercel and Next.js.
It is good to have friendly competition! Would keep Next on it toes to do not slack up! :D I never used Vue, but I think it is good in some ways, because saw job wanted this in requirements. There are free courses for Vue, but I do not want to learn Vue. Something about it is just not my type. I very like Vite though, and respect the work of Evan You and Anthony Fu !
adding more new features they will deprecate/add breaking change in next 16? I'm so glad I stopped following these releases, no need of FOMO when using next lol
What features from the last two releases are deprecated or broken now? They've been awesome with backwards compatibility, moreso than almost any other framework
Here’s a summary of the key points from the video with timestamps:
****00:00** - Introduction to Next.js 15**
- Next.js 15 released just before Next Conf.
- Major focus on making the framework easier to use, with much-needed changes.
****00:22** - Sponsor: Clerk**
- Discussion on how Clerk simplifies authentication (SSO, multi-factor, passkeys).
****01:08** - Stable Release of Next.js 15**
- Next.js 15 is stable and ready for production.
- New `next@codemod` introduced to help update codebases automatically for async changes.
****01:35** - Breaking Changes (Async)**
- Some breaking changes related to async behavior.
- Example: Previously, calling `cookies` did not require `await`, but now it does. The codemod automates these updates.
****02:27** - Caching Defaults**
- Caching behavior changes: `fetch`, `get` route handlers, and client routes are uncached by default.
- Explicit caching must now be specified.
- New caching options: `no-store`, `force-cache`, and `static`.
****03:45** - Page Components No Longer Cached by Default**
- Page components are no longer cached by default, ensuring fresh data when navigating.
****05:07** - React 19 and Compatibility**
- React 19 (RC) is used with Next.js 15. Pages Router remains compatible with React 18.
- React Compiler is out of beta.
****06:22** - Next.js 15 Aligns with React 19**
- Next.js aligns its release with React 19 to minimize future delays.
- Backward compatibility with React 18 remains.
****07:32** - Pages Router Support Continues**
- Pages Router will continue to be supported for new and existing projects.
****08:22** - React Compiler Eslint Plugin**
- React team’s eslint rules were refined during the creation of the React Compiler. Recommended for all React apps.
****09:16** - Hydration Errors Improvement**
- Hydration errors are now more informative, providing detailed diffs to identify issues.
****10:30** - Turbo Pack for Dev Mode**
- Turbo Pack is the new default for faster development builds. It's not yet ready for production builds but will be soon.
****12:45** - Static Route Indicator**
- New static route indicator helps developers understand which routes are static or dynamic during development.
****14:02** - `waitUntil` and `after` for Async Operations**
- `waitUntil` and `after` help handle asynchronous background tasks more efficiently on platforms like Vercel.
****16:21** - Instrumentation.js for Error Management**
- Introduction of `Instrumentation.js` to improve error tracking and logging, especially for platforms like Sentry.
****17:16** - Form Component**
- The new form component supports prefetching and client-side navigation with progressive enhancement.
****18:39** - TypeScript Support for Next Config**
- Next config files now support TypeScript, making it easier to see keys and experimental flags.
****19:56** - Sharp Package Included for Image Optimization**
- Sharp is now included by default in Standalone output mode, simplifying image optimization.
****21:26** - Server Actions Security Drama Resolved**
- Security concerns with server actions were addressed through encryption and randomized IDs.
****24:44** - Bundling of External Packages for Servers**
- External packages are now bundled server-side to improve performance, particularly in serverless environments.
****26:04** - Server-Side Optimization**
- Next.js now allows control over bundling external server-side dependencies for improved cold start times.
****27:47** - Improved Static Generation**
- Static generation speed has been improved, and fetch cache sharing across multiple pages is now possible.
****29:28** - Concurrency Controls for Static Generation**
- Advanced controls over static generation, including worker concurrency, are introduced to speed up resource-intensive tasks.
GOD sent!
Thank you, crazy videos in 2024 doesn't have timestamps by default.
Bless you
@@SpeakChinglishI wouldn't be surprised if that happened by default for RUclips Premium users but not for regular users.
Is it just me or is this comment generated by ai?
we’re here for the use cash 🤑
Pure pa$$ion
If you write: ‘use cash’ at the top of your files, they deploy automatically to vercel at premium prices
Good one 😂
haha
'use cache' for developers, 'use cash' for Vercel
🤣
good one 😂
We gunna see Nextjs20 before GTA 6 💀💀
We’re gonna see all of those before Half Life 3 😢
why're you waiting for gta 6? I bet it will be disappointing for a lot of people. Authors of first 4 parts doesn't work on it any more
@@Disorrdersrsly remember how disappointing Duke Nukem Forever was?
@@DisorrderExactly
lets go, time to rewrite my entire project
then rewrite it to remix and thank me later 😎
Dear @@Adityacode,
oh hell nawl
Kind regards,
@_raptor4070
How is remix? I tried solid but I still feel.like it's all messy@@Adityacode
@@Joshua.Developer I'm switching to Remix. Next.js is just painful
@@Joshua.Developer remix doesnt give you much fancy things, its route based data loading and route based actions just like a traditional server rendered app but most people just hear this and assume that you would have to just prop pass everything to components but tbh its a skill issue. Remix has some great hooks like useMatches for that problem and error boundaries are so great, you get to learn so much about the web like http caching and how easy it is to cache. For example, I implemented my own route cache that allows me to cache which ever route i want to, not like next js route cache that you cant change. Honestly, only things remix lacks is middleware and type safety in actions easily.
Really love the hydration error logs
12:43 I like it! Tiny little thing, but so much value! You get to know if your page is static right away :D Also, you can see if page is static after build in console
I’ll be using 14 for the foreseeable future. Totally fine for any project.
James from Payload CMS said he'll have the 3.0 version out in a few weeks since Next 15 is now stable
he previously said they’d release it as soon as it was out. and in March of course they just needed to update docs to release lol
Stable
clerk is doing evil shit with their pricing lately. you need to pay for their super premium tier in order to impersonate users - something which is tablestakes in other auth provdiers
MFA for $100 is just as bad. Like wtf? That's the bear minimum.
Hey guys, forget nextjs, Sveltekit v5 is out
That's Svelte v5 for ya not SvelteKit
How do you shortcut between ur browser and ide in one button? That’s so cool and I can’t find any simple way to do it after searching
15:39 - what is the difference between using the after API, and simply creating a Promise and not awaiting it?
Done with nextjs forever, remix or other framework is the way to go now. I'd rather use angular than be forced back to nextjs
sveltekit can be a greate alernative!
@@Sub-05-19 Yapp agree, but sadly for my workload react is still preferred because of its extensive support in Web3 libraries and even other libraries.
I've heard only good things about remix.... Very very tempting
@@Sub-05-19 I'm liking sveltekit too but I have next js in my job. is the support for svelte 5 stable release now?
@@reilwaystation4372Yeah it's stable, that's what the developer said on the blog post but don't just take anyone's word for it, try it out yourself!
Fantastic changes, thank god
Hey Theo 👋 Very Nice Explanation ❤
Another day another update in the Javascript world, I cant keep up
50% of hydration errors are caused by date usage, and the other 50% are caused by local storage usage 😂
ehhh, i'd say there's a good 10% "you can't put that html in there"
Looks like I will have to wait some time to upgrade since framer-motion code breaks after upgrade. Won't even build. Complains that className is not valid anymore on motion elements. Might be a simple fix but I would rather not risk breaking the live env.
You need to update framer motion to v12 canary to fix that className type issue. Still not recommended to upgrade to Next v15 since React 19 stable isn’t out yet
and here i still use page route
How do you so quickly siwtch windows between editor and browser?
Bumping this. I need an answer
maybe something like streamdeck or whatever they're called with customizable keys
Alt + tab
@@thecodingchef9292 He is on mac
How can Vercel release Next.js 15 before React 19?
they use the RC canary channel which (as the react states) it can be used from libraries
The same way Instagram already use the React compiler in production
@@dmsnmgood to know
insider job
does the Nextjs solve the router events problem for app router? in pages router, we had routeChangeStart, routeChangeComplete and routeChangeError which are crucial in pages that have forms and help to prompt users if they really want to leave the page without saving what ever they were doing. but this event were not available in app router. so is this feature available in nextjs15?
I'd love to see some detailed video on NextJS caching and CDN configs in Fastly for example.
Why would you say the component is more like a remix thing over a next thing?
They dropped it early because Svelte 5 dropped.
No, thanks. Remix (React Router) is the only sane way.
Exactly 🤝
no tanstack router is the way
I looked into this. I thought remix was still using the old router and the new one hasn't come out yet??
I need to learn Remix.
Sorry, but v15 is not stable for production if React 19 is not stable.
Ikr, this is fking insane…
Facebook and instagram are using 19, you should let them know that they aren't stable for production.
@@hello19286How did using an unstable version of React work out for Next in v14?
I imagine it’s not quite that straight forward with re: FB and Instagram.
It should be stable till you reach your production deployment deadline
Thanks for this video! Would love to see a video that shows you upgrading a real project that uses ShadCn/UI. For me, it does not work at all as the radix-references fail. As a relatively new NextJS developer, this would be very helpful to see how to deal with "third party" packages when upgrading.
Bumping cause so true
How does that react eslint work if I wanted to use biome instead?
how much of this I need in case of livewiew ?
This release was really unexpected.
Hydration Hydration Hydration errors everywhere
LMAO couldn't agree more. Had that recently after upgrading from v14 to v15
Thank god they are finally getting rid of their ridiculous caching by default BS. That was such a bad decision on their part. The other thing that annoyed and shocked me was when I was doing a build and it was trying to connect to my database. I was like WTF, why are you trying to access my DB at build time?
I just finished migration from app route to pages router because of the insanely cache enforcement lol
theo be looking like the kid from love actually fr fr
How do you switch from the current app to the browser? how did you asigned the hotkey?
Alt + tab
Any updates in t3?
What is the site at 11:10 ?
Really excited about this version
29:05 ...can someone help me how to zoom like this? is it some bind of recording software you are using (probably OBS?) or is it something i could achieve with basic macos screen recording?
Finally his video came out.
Thanks for the info.
Kinda funny that clerk is the sponsor because it's not fully ready for next 15 right now. They merged the PR for next 15 compat but haven't released it yet...
From a mere technical and un-opinionated pov it seems that for the most part they just fixed some "dumb" bugs or weird decisions/assumptions they have made in the last 14 versions... (14!!). I'm not blind: I can see why a lot of peoples are using Nextjs and why there is a lot of hype everytime they just "fix" something that in another stack regular devs will throw a pile of s...t against, but from a dev which is actively in the industry for 20 years sorry, but I still don't buy it (but this is just imho): when they release Next16 maybe they will point at all the mistakes done in Next15...
However I recognized that is still a framework with a lot of features, especially for modern frontend (but I do not understand why not using Vite as default btw) when other "batteries included" solutions don't have such solid concepts (or at least into the core and maintained by core team members). Happy coding everyone!
facts. Ive try to move away from using next, too much changes.
I was so hyped about 13 and 14 but it really is painful. Especially the default caching in 14. Vercel made programming stupidly more complicated. If they want devs to experience the cool things of Server Components, Server Actions, then just implement it and hide from us. I'm switching to Remix and I hope they will do RSC better than Vercel's
Any senior front-end Dev knows Next is a joke and preys new coders, stick with what works for 5 years of React and stop rewriting every 3 month
@@mickomagallanes1185 Yeah I had the same progression of hype to refactor hell and eventually biting the bullet and bailing on Next. I really dont know why we're pushing SPA inspired javascript frameworks to the server. It's the worst of both worlds.
@@shanemarchan658 I am im the middle of rewriting my projects into sveltekit or nuxt
12:01 Anyone know how to set up that hotkey Theo uses to switch between VSCode and Chrome in one click?
Bumping this cause i wanna know too
And turbopack not working in dev with next typed routes =..=
18:30 ok sure, but that is really not difficult code…. looks like every form data submission function I ever wrote back in vanilla JS and jQuery days
23:50 “weird concerns”? Really? This is one of the most popular react metaframeworks out there, with massive adoption by junior devs and total n00bs…huge target for malicious actors looking to affect a large number of sites with a single exploit. Nothing “weird” about such concerns.
Clerk is not ready for Next15, they rely on the sync version of headers(). Until they update Clerk to use the async version released with Next15 it won't be ready.
Clerk is so good
mfa pricing is dumb
@@nickwoodward819 yeah, except that
cant wait to pay vercel
yay another breaking changes
theo why do you have your file tree on the right side
I haven't even learned nextjs 14 yet 💀
you can tell theo woke up in a panic at his "next 15 released" alarm because his hair doesn't look perfect in this video
I'll stick with Angular
Sane decision!
26:31 I have strugling with eslint for so long! Every project starts with configuring this mess. I both love it and hate it. Love for simplicity of adding rules.
Hate for awful configuration and setup experince. Also in-IDE explanation of rules would make a huge difference! Each freaking rule need to go their site to read about - obnoxious!
coooll
3rd?, goto bed theo!, or if u just woke up goodmorning!
They all make shit about this framework all the year
And when it got a new update every one is hyped
At this point I’d rather use Angular than the trashcan that is NextJS
I love clerk!!! The only problem is that the UI is outdated in the pure js library
$100/month for mfa is bs.
This is like putting new tires in your car that the manufacturer didn't approve yet. It must be insane to install and use that package for now. Now try explaining to the Jr of your team why he can't depend on alpha/beta/rc now haha
i will use astro 😂
😞🤧😤 I think that if Vercel/Nextjs develop consistent solutions thinking about the next generation of applications... it will be worth it for mid-big companies to pay for services that, in the end, will save them costs in other areas of infrastructure. Good for Vercel, good features
I read every comment in this thread. Most people are mad at nextJS and want to use remix (if they need react libraries) or svelte5 which just came out. Not many people in the comments are happy with how "messy" next.js is right now. Feels like we're the canaries in the coalmine
02:04 Cat! :D🐈
Are you sure that clerk supports Next 15? I tried it and it does not work
it works but in canary version
now waiting create t3 update
2:04 cat!!!!
So another batch of complicated cache features that are broken and full of bugs? Thanks Vercel!
skill issues
@@hello19286 yeah, skill issues by Vercel
Did he say next 15 was overdue? Its been in RC for almost half a year ffs. We got an RC 2 because it was so aggregious
Hi Mr Mustache!
LMFAO at your custom url shortener literally being "soy dev"
Easier means more abstract and less detail
Next.js 15, because object oriented langues didn't die in the 90s.
Clerk? Not owning ur data? Nop
leave NEXT js for a sec. 2:11 nice cat dude, what's her/his name?
Maybe I’m in “enemy territory” here, but NextJS just feels like the continuation of “web dev is a hot mess”. Crappy dev tooling and DX.
Is there a better framework for someone building SaaS apps and “not building facebook”?
We are building B2B SaaS Platform and it's currently based on NextJS (luckily without too much serverside stuff.
Migrating right now to vite. Looks good 🌞
80kloc in size to have a reference.
Will report.
@@theSnackableCTO I’ve seen another saas kit that use Bun. I just want a highly opinionated “fast launch” solution. I don’t care about customizing build or state solutions etc.
@@utubes720 you target to build a small or microSaaS?
@@theSnackableCTO Definitely Micro, but ideally same solution for either.
@@utubes720 maybe blitz.js or redwood.js. never used them myself.
Bun ofc interesting. But maybe not yet evolved long-term. If that matters in this case :)
two months after theprimagen called out people using libraries like clerk to make projects instead of making something good, theo gets sponsored by clerk💀💀
theo's been sponsored by clerk a fair amount iirc. nothing really wrong with side stepping auth, but clerk's pricing is bs
@@nickwoodward819 tbh clerk has sponsored a lot of these tech people, I dont think I've seen a video where someone actually used clerk because it was better than alternatives, but its not the case. I dont like these type of tech to sponsor these many tech influencers, Snapdragon X elite is a great processor but on initial release it was so hard to find an independent review that it sort of makes me feel that I should not trust these sponsored reviews.
Still deployment Next.js outside vercel is nightmare…
By design.
I wouldn't hold my breath on that ever changing.
what about it is a nightmare? I don't see anything evidence of that.
@@aberba try to deploy enterprise size next app outside vercel, and compare it. Also seek on RUclips there is a lot of technical content why deploying next.js app outside vercel is rubbish
@@coder_one is Remix better for enterprise?
@@coder_one how is enterprise deployment build different from regular VPS deployment build? Again you haven't mentioned a thing except there's some complaints on RUclips
Vercel started pay money again?)
Next image background size cover when?!
A long time ago?
what?
@@maciekdeveloper There's a 'fill' prop, an 'objectFit' style, and if you need your image as background, you can do it with the 'getImageProps' function
@@maciekdeveloper There's the `objectFit` style, the `fill` prop, and if you want your image as background, you can do it with the `getImageProps` function. What else is missing?
There's the `objectFit` style, the `fill` prop, and if you want your image as background, you can do it with the `getImageProps` function. What else is missing?
Next is garbage. I am so grateful to be working for a company that uses vue. Next has been systematically destroying React. I can't begin to express how much I dislike Vercel and Next.js.
Why even writing it here?
@@nefed-Lbecause he can
It is good to have friendly competition! Would keep Next on it toes to do not slack up! :D I never used Vue, but I think it is good in some ways, because saw job wanted this in requirements. There are free courses for Vue, but I do not want to learn Vue. Something about it is just not my type. I very like Vite though, and respect the work of Evan You and Anthony Fu !
adding more new features they will deprecate/add breaking change in next 16? I'm so glad I stopped following these releases, no need of FOMO when using next lol
What features from the last two releases are deprecated or broken now? They've been awesome with backwards compatibility, moreso than almost any other framework
4th
Let’s boycott nextjs 😂
Next! 😂😂😂
I'm switching to Svelte 5, I hate Next 14.
First😊
He did it!
Congrats! :D But next time better write something useful for others too :D Although it is fun to see such coments :D
You don't need this stupid framework to make a website.
Fr! All in with Php and spring boot
@@srujangurram how do you combine the two?
Don’t use it and save the hate.
You do not, but I like it, works well for me, I enjoy using it, and it earns me 6+ figures every year.
You don’t need code to write a website. I just telepathically send all of my html css and js and render them in my clients mind.
Sso mfa
I have come to the conclusion that I hate NextJS.
thumbs up if you want theos video to be shorter
Clerk is shit