PM2 is the way to go in my opinion. Here is a short presentation I did on PM2 http://slides.com/artizan/pm2 You can find guides and tutorials on digitalocean knowledge base. Good luck!!

Does your stack have a name? As you can see in the link bellow there are many many available stacks. I was interested particularly in those two since I know many of the hashnode community are involved... http://andrewhfarmer.com/starter-project/

IMO - You don't have to use any type of "Grid system"... No external libraries are needed . Just use Flexbox instead. it has native support on all browsers . And it is fun and easy to learn :)

Prashant, none of the examples around show how to use JWT with passport-facebook All of the examples I've seen around stop at passport-local or your own email/password. None go the extra mile to demonstrate how to implement 3rd party Oauth like facebook or twitter using JWT. I don't need to tell you that Facebook and other social connect buttons are the standard since they are implemented on Hashnode as well. but somehow they are always overlooked and nobody ever demos how to implement JWT with a Facebook strategy. No one! This is extremely important and essential and all answers avoid this point. why? Why won't you demo how to implement a social connect with JWT using Mern? This is not Trivial. not at all. Please consider to. Thank you.

Any argumentation to support your vote?

I vote for Domain based structure .

My thought exactly, but the whole point of having a starter project is that it is ready for use. If it's not that big of a deal, please try and modify Mern-starter to accomodate it. I know babel parameters very well. It's not about that. it's about deciding how to compile the server with babel and the current folder structure while having webpack compiling the client. The current "build" script refers only to the client compilation by webpack. It compiles it into '/static/dist/' folder. Where would you suggest to compile and run the express server using babel-cli?

Bluebird JS by far! Jquey promises are based on an old spec and not the final one. For general promised based code Bluebird js has the best performance and the most features. Here is a deck I've prepared about Promises for newbies For Promised based Ajax calls use fetch which is becoming more available on Browsers. If it is not available however - use the Pollyfill ... Enjoy :)

Hey @agilius :) checking if process exists gives us the same true/false indication as when checking if window exist since niether exist on both client and server. Also - this check needs to be done at run-time and not at compile-time so therefore cannot be used within the webpack config. checking the env in webpack is relevant since you may want to pack your app differently for dev use or production use, however in the case I was referring to the component needs to check where it is being rendered since in isomorphic (universal) apps the react redux code may be rendered on both server and client so I needed to avoid a dependency on window if it is being rendered on the server... hope this make sense. in any case this problem is solved for my needs :)

Hey @whotheheck :) The intention was referring to code written inside a react component needing to know if it runs on the client or the server...