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).

Hello Sandeep, I have a doubt, why did you decided to change from MERN stack (the MERN stack you were developing)? I mean, the main points that made you move. And as a personal question what do you think would be the killer and the best points about this type of stack? I ask this because I'm starting to search for other options like next.js, sails.js, adonis.js and others since I got discouraged by the lack of maintenance. What advice could you give about this subject? (change, continue to use it) Regards!