Комментарии:
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?
ОтветитьThanks, I didn't want to watch the whole conference, this is to the point and a good summary
ОтветитьThe truth is using Nextjs is really annoying with server side and client side stuff, awww
ОтветитьWhen nextjs have better middleware and Request handlers, let me know
Nextjs is still for building basic websites
kyle you take up too much space in the video...
ОтветитьNextJS became PHP as I know it from my very early career... Blee
ОтветитьShake shake
ОтветитьAfter seeing so many updates & improvements I am one of very few devs who will prefer pages router over app router or remix
Ответитьa few more adds would be great
Ответитьthanks
Ответить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
Ответить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
Ответитьfirst thanks a lot for this useful video , what is your vscode icon theme bro??
ОтветитьThanks for the awesome video! Do you have any plans to cover the new ESLint 9? Would love to see it!
Ответить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 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?
ОтветитьThanks for clearing everything, man ❤
ОтветитьInteresting, I would expect Biome to be an option instead of just ESLint 9… but I guess is like pnpm, will take time…
Ответить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
Joined by recommendation.
Ответить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 ?
ОтветитьI'm sick and tired of this react next stupidity, f'em! 😡; Moving to svelte and sveltekit
ОтветитьWhat an hot mess of beta, release candidates and dirty fixes. Am I expected to use this for work?
ОтветитьCurrently watching your next js course seems like I'll wait for the New one 😅
Ответить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) ?
ОтветитьBro is looking older lol, been a subscriber for 5+ y now ..
Ответитьgreat coverage! thanks for rerecording
Ответитьthanks Kyle love your videos man, this was really helpful.
Ответитьbeautiful 👀❤️❤️❤️ ... that said let start listening him😂😂😂
Ответить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... :)
ОтветитьWas never a fan of NEXT and really only watched this to find out why I still don't want to use it.
ОтветитьBest!
ОтветитьNext auth, Mongodb, stripe don't work on it no more.
ОтветитьWe would like to see you playing that guitar 😊
ОтветитьAlways on point, Kyle! Thank you, I get up-to-date thanks to you!
ОтветитьSay no to next js❎ only pure js ✅
ОтветитьIt borke backwards computability for lot of library
ОтветитьI guess I will be in next 14 for a while and upgrade to next when the stable react 19 is supported.
Ответить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.
I feel remix is better than next.js. Atleast it has very few and stable updates. I'll learn remix.
Flutter Dev here: I love Next ❤
ОтветитьEverything I need to know? In 18 minutes? I hope you're right!
Ответитьso much change, if project existed you should not upgraded it 😢
ОтветитьOh cmon just when i started a next14 tutorial series
Ответить