HACKER Q&A
📣 teaearlgraycold

I'm abandoning NextJS. What's an alternative full-stack TS solution?


It feels like NextJS is trying to build back-end tech specifically for people that don't want to write a back-end. That seems like a recipe for disaster. "use server" looks to me like a feature you should be very careful with. But if someone's using it specifically because they're lazy they probably aren't going to be careful.

What I liked about NextJS:

* server-side-rendering is definitely a plus for the user experience

* being able to check cookies before sending the user any data is great (a basic requirement that many SPAs didn't used to do)

* the built-in router was nice

Previously I've had NextJS front-ends calling NestJS APIs. What are my options here? Any good example boilerplates?


  👤 cliffwarden Accepted Answer ✓
The community here is pretty friendly. https://redwoodjs.com/

👤 catlover76
I would throw out the option of just choosing your favorite lib for each component of the stack, and using them in conjunction.

I would also point out that the 3 specific points you mentioned have all been basic assumed features of web frameworks since 2012/2013 lol


👤 wdb
Remix? It’s one of the cool kids on the block