Popular posts

Our codebase is still based on MERN stack. An interesting thing is: we released mern-starter much after building Hashnode. So, we never really rewrote Hashnode using this boilerplate. However, we just took the good parts from mern-starter and incorporated it into Hashnode.

IMO, Next.js does an amazing job at helping people build server rendered React apps that just work. It's well maintained and has amazing docs/support. Plus it's nothing but React and Node.js. So, when we rewrote Hashnode in early 2018, we just went with Next.js as it was simply the best option out there. So, my recommendation is to go with Next. :)

Ok ok, thanks for your response :). I'll definetely take it into account for future developements. Even though I've made the decision to continue and improve your initial framework and so far it's great, I love that it can be personalized so I already affected both mern-cli and mern-starter according standards that I've been working on before with other frameworks (mainly laravel) in my workspace. If you can still do a small push to your old proyect (mern-cli + mern-starter) it would be great though. Furthermore, maybe a naive question, but who is maintaining those proyects? I mean, if I push changes, is someone doing the merge or I'm able to do that changes myself. Finally, would that repository be reliable? I mean, do you have any plans to delete it? (thinking to create a back up repository so that everyone can still use it or improve it).