create-react-app

create-react-app now uses some kind of extensible build scripts in form of react-scripts: webpack files which you can clone and modify and use without ejecting. here's one for less: https://www.npmjs.com/package/create-react-scripts-less also here are the official docs: https://github.com/facebookincubator/create-react-app/blob/m...

Have you ever tried a tool like https://github.com/facebookincubator/create-react-app ? It makes your comment totally irrelevant.

Requirements vary per users. If you want a zero-conf solution, you can use create-react-app [0]. I use fish as my shell because it has far more sensible defaults than bash and zsh, but I understand why they can't just "fix" the quirks. Fixing their quirks and changing the defaults would likely break tons of existing scripts. This pretty much goes for every large software project. As another example, consider many of the web's defaults. You need to specify the doctype or you get quirky legacy behavior. If you don't explicitly specify utf-8 as the charset it'll try its best to guess [1] and will likely default to the wrong value. And don't get me started on CSS! I think the complexity is being overblown though. Take a look at the build scripts for some truly huge projects like Android or Chrome. Now those sure are insane. Trying to figure o

they look pretty similar to me, one is kinda like js-in-html, the other is html-in-js, to each their own. I'm talking more about the whole experience of building out a full app. How do I structure my codebase? Which packages should I use in 2017? It's a much more trivial exercise with vue if you're only doing frontend work occasionally and not as part of your normal job. I have to point out that https://github.com/facebookincubator/create-react-app is great if you do decide to go with React and want answers to aforementioned questions.

I implore you to checkout create-react-app to get a hello world really quick: https://github.com/facebookincubator/create-react-app npm install -g create-react-app create-react-app my-app cd my-app/ npm start Your sentiment is correct that tooling around these pieces of technology needs to always be first class. React failed miserably, and Vue did an AMAZING job. I'm probably starting to sound like a shill for React. I've used both and love both. I do like that React is "just javascript", which I think is why I use it.

FYI react-create-app also has PWA features: https://github.com/facebookincubator/create-react-app/blob/m...

There are a bunch of linked issues at https://github.com/nodejs/node/issues/13815 and https://github.com/npm/npm/issues/16991, such as https://github.com/facebookincubator/create-react-app/issues....

Looks promising https://github.com/facebookincubator/create-react-app ! That's the one part of the stack I still need to learn (becuase jQuery is not trendy anymore apparently)

Stick to https://github.com/facebookincubator/create-react-app/ and you'll be golden. If you need more config later, you can "eject", but this is a one-command-and-go kind of thing that is well maintained and works great.

I think an interesting reflection when considering the config setup difficulties of Webpack are the so-called 'zero-config' projects like; https://github.com/insin/nwb https://github.com/saguijs/sagui https://github.com/mozilla-neutrino/neutrino-dev https://github.com/facebookincubator/create-react-app They help frame this domain's perspective on the timeless tension between usability and flexibility - ie am I prepared to sacrifice some configuration options in return for being able to get quickly setup? Clearly the answer in a lot of cases is going to be 'no', but nevertheless seeing how difficult it can be to find that sweet spot between usability and flexibility might help one better appreciate the value returned by those difficulties. Personally, I've found the commitment to stick to the conventions enforced by Create React App to hav

1) Create a react app with create-react-app [0]. 2) Add bootstrap as specified in their README [1]. 3) Profit. [0] https://github.com/facebookincubator/create-react-app/ [1] https://github.com/facebookincubator/create-react-app/blob/m...

Honestly you should not use a React boilerplate of any kind as of today. We got pretty decent alternatives today in order to avoid using that kind of stuff: - You're just getting started with React? Use CRA[1], it is enough for most of the use cases people will ever need use React with. You may also want to consider Next.js[2] if you are looking to do a more website-like app using React components but that's all... - You know how to setup js tooling (webpack, babel, react-router, redux, ...)? You may still want to use CRA because it is way easier to use anyway. But this time you know you can either eject to more fine-grained tooling tuning or do your thing independently if you want. If you use a boilerplate at that point, that's because you understand the tooling behind it and CRA won't answer to the precise need covered in this boilerpla

I think the issue the parent is referring to is that CRA's Webpack configs only define a single "entry point", for your index.js, where each entry point becomes a separate bundle in and of itself. Having multiple entry points, like an "app page" and an "admin page", would require editing the Webpack config, which CRA deliberately keeps abstracted and hidden away until you eject. If you really want to be able to modify the Webpack config for a CRA app, you have a couple other options besides ejecting: - Create your own custom fork of the react-scripts ( https://github.com/facebookincubator/create-react-app/tree/m... ) package that CRA uses - Use the react-app-rewired (https://github.com/timarney/react-app-rewired) tool , which lets you override parts of the build config within your project.

I love create-react-app too, but for a slightly different reason: They have an excellent, super-comprehensive README that covers practically everything you'd ever need to know about state-of-the-art Frontend JS tooling: https://github.com/facebookincubator/create-react-app/blob/m... create-react-app itself is great for quick prototyping, but for non-trivial apps, chances are, eventually some esoteric production concern will force you to "eject". At that point, the sheer volume of configuration you'll be left with will be rather overwhelming if you've never dealt with the underlying technologies before, and modifying/extending it can become rather intimidating. My recommendation is to start your first few projects with create-react-app, to get a feel for what a modern JS dev experience feels like, and then once you find the need to eject,