Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Server actions vs API routes in Next.js

59,223 Aufrufe • vor 1 Jahr •via X (Twitter)

10 Kommentare

Profilbild von Abod 🚀
Abod 🚀vor 1 Jahr

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

Profilbild von Alex Sidorenko
Alex Sidorenkovor 1 Jahr

🫡

Profilbild von Designly
Designlyvor 1 Jahr

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

Profilbild von Koka
Kokavor 1 Jahr

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

Profilbild von Alex Sidorenko
Alex Sidorenkovor 1 Jahr

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

Profilbild von Garrett
Garrettvor 1 Jahr

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

Profilbild von Daniel Noworyta
Daniel Noworytavor 1 Jahr

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

Profilbild von Alex Sidorenko
Alex Sidorenkovor 1 Jahr

Apple Keynote + Screen Studio

Profilbild von Alfon
Alfonvor 1 Jahr

🔥🔥

Profilbild von Paul @ Deterministic Design
Paul @ Deterministic Designvor 1 Jahr

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

Ähnliche Videos