正在加载视频...

视频加载失败

Server actions vs API routes in Next.js

59,223 次观看 • 1 年前 •via X (Twitter)

10 条评论

Abod 🚀 的头像
Abod 🚀1 年前

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

Alex Sidorenko 的头像
Alex Sidorenko1 年前

🫡

Designly 的头像
Designly1 年前

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 的头像
Koka1 年前

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

Alex Sidorenko 的头像
Alex Sidorenko1 年前

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 的头像
Garrett1 年前

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 的头像
Daniel Noworyta1 年前

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

Alex Sidorenko 的头像
Alex Sidorenko1 年前

Apple Keynote + Screen Studio

Alfon 的头像
Alfon1 年前

🔥🔥

Paul @ Deterministic Design 的头像
Paul @ Deterministic Design1 年前

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

相关视频