I'm a bit confused about this. Why does Next.js seem to make this use case so complicated?

If my backend is completely separate from my frontend, do I still have to use Server Actions or API Routes just to hide the backend endpoints from the client?

If not, is it perfectly fine to use Next.js essentially as React and call my backend APIs directly from the client? Am I missing something?

looool

lolo

hrtertergrrterter rt

#rter

fghgzrtgfhgtzrtedgfr

36

<hello>

lol

:)

404

qwerty

This still doesn't make ***

*** sense though!

Hello

adsf

what what

hello gays

wasup

Released a 90-line app that turns my voice memos into todo items. It will never get a landing page. I use it every single morning. #shipping

v2 of `react-cmd` is out. Same command palette, half the bundle, full keyboard support. It drops into any app and works without a provider. #opensource

Released a CLI that scaffolds the project structure I've argued for in every PR review for three years. If you've reviewed my code, then yes, this is that structure, now in one command. #opensource