Загрузка видео...

Не удалось загрузить видео

На главную

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

Похожие видео