DEV Community

Discussion on: Is it a good idea to use CLIs to generate projects in JavaScript?

georgecoldham profile image

I created a simple React boilerplate that is ready for production with its webpack config. I use that for every new React project and its as quick as create-react-app to get going. Difference is I know how it all fits together, and if theres an issue I can understand why.

create-react-app I feel is good to get going, but doesn't provide a way to deliver refined production ready code without making larger changes to the underlying structure. Something that I feel is more dangerous after working on a project for months. Its like trying to add plugs to a house thats already built, its possible, but really irritating and messy. It would have been easier to do it from the start.

I have very limited experience with Java, my understanding is that it is much more static than JavaScript. And if JS were to sit still and create-react-app would stop changing etc, then I would feel more comfortable about recommending it. It sounds like Spring has much more solid foundations than anything in JS really does at the moment, so it seems fine to me.

Ultimately, while I would recommend learning how React and its surrounding architecture works by building your own at least once. Once you understand it better then who am I to say dont/do use something? As for other frameworks, no idea... If its for a hobby project then go for it especially, no point wasting time on something you will never need to know.