[Nkuna]

Next¹ offers a more fleshed out framework with far less boilerplate for both client and server code.

Server side, Nest² offers much of the same. Think Angular but for backend dev. Yes, it has some boilerplate to it but for the most part, its CLI eases redundant typing.

[1] https://nextjs.org/ [2] https://nestjs.com/

[slow_donkey]

You can be productive with Nest.js but I'd hate to promote it as a great solution. It's really a mashup of other JS libs with Nest bringing a rather convoluted form of dependency injection and http action decorators. You can build your own soup rather easily without the Nest overhead and with better choices. It's not the worst place to start, there's just better shit out there.

[hermitwriter]

I don't know. I use next.js and love it. But I have to implement two static methods for every thing I want to fetch... This also locks me into next.js...

[eyelidlessness]

I’ve shopped around a lot and most projects targeting a similar featureset are generally adopting the Next.js APIs for server-side data fetching. So it’s probably not as bad in terms of lock-in as you’d expect.

[xeon06]

I think more people should take a look at https://blitzjs.com. It makes your lock in problem slightly worse I suppose but only because it argues that you want most apps to be coupled like this in real life. In exchange, it gives you great developer experience around things like data fetching.

[scsilver]

Touched this about a half a year ago. Feels like rails for react. Very opinionated and interesting how prisma is used to set up the data schema.