Mega Boilerplate

Handcrafted starter projects

#3 Product of the DayJune 08, 2016
Would you recommend this product?
1 Review5.0/5
Holy shit, this is amazing! Really good job on this Going to explore the docs more but so far looks like this will replace yeoman
@kevinyun Thanks! Please let me know if you have any suggestions for the README. It is still very much work in progress.
Hey all, I am super excited to share with you this project that I have been working on for over 7 months now (my biggest one yet). The idea behind it came from one of my earlier side-projects called "Hackathon Starter", but unlike it, you are free to customize any part of your stack. Please feel free to ask me any questions you may have about the website or the boilerplate code! Also feel free to reach out to me by email at
THIS IS INCREDIBLE. Would love to see a similar solution for Rails projects.
This is really awesome @evnowandforever! I would love to see an option (like with the database or css framework categories) for no template engine rather than having to use either Jade/Handlebars/whatever. Just use React/JSX or vanilla js, for instance - just a thought. To try and catalogue all that one can do on the web today is incredibly helpful and inviting. Great job man, looking forward to updates!
@peteallport Thanks Pete. What you suggest is something I have already considered during the early days of Mega Boilerplate, but decided against it to keep things simple. But I know what you are talking about. The main challenge here is not even the extra work but rather UX. Let's say a user selects Template Engine "None". Then continues to CSS Framework, CSS Preprocessor, and then decides to select "None" JS Framework (No React, Angular). At this point Mega Boilerplate won't be able to generate anything meaningful since neither template engine nor JS framework were selected. I guess I could disable "None" JS Framework option if Template Engine is already set to "None", but I'd like to hear your thoughts on what would be the most intuitive and easy to follow solution.
@evnowandforever I'd imagine that you can very easily go down a dark path of complicated combinations haha. I think you're right though, to then require a js framework if not already selected would be optimal. Either way, cheers! πŸ‘πŸ»
@evnowandforever @peteallport Seems like the tool is still useful with no frontend - you could, for example, make an Express app with Mocha and a Mongo connection. You can maybe show the user a pop-up message letting them know there won't be any frontend components in this case.
@clay_to_n @peteallport I've have similar but opposite suggestions where someone wanted just the front-end - React or Angular app without any server code. It is certainly possible and shouldn't even be that difficult to implement. I will consider splitting into API only and Front-end only boilerplate generators in the near future.
@evnowandforever @clay_to_n agreed Clayton, and Sahat I wouldn't think there'd need to be a separate flow for apps w/o a frontend? Maybe I'm misunderstanding. I suppose it's just a matter of organization. I really like the idea of a popup message for no frontend.
Hey Sahat, just built a boiler plate ... the options were very impressive! I'm curious how you're generating all these super specific scenarios?
@noahtovares This project consists of hundreds of micro modules (files) that are composed on the fly. I start with a base file, e.g. server.js, which contains a bunch of comment strings that are removed or replaced based on user's choices. The idea is really simple, it's just very time consuming, hence it took so long to build this project.