At any given point in time, you can type “react starter kit github” and find a plethora of ready-made kits to get you started on your next project. I am certainly not the first person to have this internal debate, and started my research by picking through the packages.json of the popular starter kits to see what everyone is using. My biggest takeaway from this endeavor is that it is truly amazing (and at times, befuddling) how many options we have available.
After realizing that I might be reinventing the wheel, I found some blog posts on React starter kits and a few of them were very helpful. A Josh Habdas post titled Awesome React Boilerplates was the first result to come back and was probably the most helpful. It provides a listing of React starter kits along with a brief explanation and links to the kit itself. If you are trying to figure out which starter kit you want to use, this is great place to start.
So back to the original question…do I create yet another React starter kit? In my humble opinion no–at least not at first. Take into account what your team knows and is comfortable with, then choose a starter kit to begin your journey. After working through things, take what you have learned and evaluate whether another starter kit serves your needs better (or, if you want, go ahead and create your own). There are so many options out there that choosing just one can be hard and ultimately it depends on your situation…but don’t we all want to hack away at something?