Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Server actions vs API routes in Next.js

59,223 görüntüleme • 1 yıl önce •via X (Twitter)

10 Yorum

Abod 🚀 profil fotoğrafı
Abod 🚀1 yıl önce

First time feeling like the App router isn't confusing, thank you for the explaination

Alex Sidorenko profil fotoğrafı
Alex Sidorenko1 yıl önce

🫡

Designly profil fotoğrafı
Designly1 yıl önce

Man, I wish I had known the difference a year ago when i was making a messaging web app, and ended up using api routes, server action, and server components altogether in that project. 😂shi was slow af

Koka profil fotoğrafı
Koka1 yıl önce

why use useSWR for fetching? isn't the standard fetch enough for data fetching?

Alex Sidorenko profil fotoğrafı
Alex Sidorenko1 yıl önce

Standard fetch is enough. But you usually end up re-creating your own version of Tanstack Query/SWR as your app grows. However, with the App Router, start by fetching in server components. You might not need that much client-side fetching in the first place

Garrett profil fotoğrafı
Garrett1 yıl önce

Nailed it – especially wrt to talking to multiple clients. You can take it a step further by using by @ido_pesok to expose your server actions consumable via endpoints

Daniel Noworyta profil fotoğrafı
Daniel Noworyta1 yıl önce

What are you using for animations? :) Gr8 job!

Alex Sidorenko profil fotoğrafı
Alex Sidorenko1 yıl önce

Apple Keynote + Screen Studio

Alfon profil fotoğrafı
Alfon1 yıl önce

🔥🔥

Paul @ Deterministic Design profil fotoğrafı
Paul @ Deterministic Design1 yıl önce

“What I’m saying is that when you’re ready, you won’t have to.” - Nest.js

Benzer Videolar