←back to thread

Next.js is infuriating

(blog.meca.sh)
1033 points Bogdanp | 1 comments | 02 Sep 25 06:57 UTC | HN request time: 0.199s | source
Show context
Demiurge ◴[02 Sep 25 14:21 UTC] No.45103496[source]▶
Maybe this is a good place to ask... but I was actually considering Next.js as a replacement for Gatsby.js project that is a few years old, but is growing at a steady pace. Given all the negative sentiments, what are better alternatives? I don't even use any SSR, or GraphQL capabilities. The main thing I liked about gatsby vs previous "bring your oown library(router)" are: very little configuring, nice dev server, easy to use plugins. It just solved many of the boilerplate tasks for me, and let me get on with react.js components, hooks, etc. I use Django backend for API, and static hosting for the frontend.

Potential alternatives I've found:

  * astro
  * remix
  * back to react-router... and there were multiple back when I used it! :(
Update: after some research, I really Tanstack router approach: https://tanstack.com/start/latest
replies(4): >>45103587 #>>45103608 #>>45106199 #>>45114309 #
1. mpeg ◴[02 Sep 25 14:28 UTC] No.45103587[source]▶
FYI remix doesn't really exist anymore, it was folded into react-router a while back.

Astro I've found to be pretty solid for prototyping, I like that it gives you control over the rendering of client side code islands and that it works with multiple rendering libraries. I don't love some of the direction they've taken lately though, and I worry that it will become bloated with things like astro db