3 ms·
What’s wrong with using webpack under the hood? The problem is webpack being a lower level tool. This is why we abstract it away from you (and we can swap it fo
by danabramov 10y ago
What’s wrong with using webpack under the hood? The problem is webpack being a lower level tool. This is why we abstract it away from you (and we can swap it for something better if it comes along, but actually webpack is pretty powerful).
- abritinthebay 10y agoWe discussed this on Twitter Dan, fyi, no need to rehash here. But they very fact you had to spend time abstracting away WebPack speaks volumes IMO...
- danabramov 10y agoSorry, didn’t realize it was you :-) >But they very fact you had to spend time abstracting away WebPack speaks volumes IMO... Speaks volumes about its poor public API. I don’t understand how this this affects create-react-app, really. But if you can suggest something better that solves the same problems, please do.
- abritinthebay 10y agoAs I think I said on Twitter - it's not really that I think something solves the same problems better; it's that one tool shouldn't be solving all those problems (and in fact many of those problems aren't in the JS space at all). Sort of... think UNIX philosophy vs... I dunno, Windows I guess? With the way it currently does it you are always going to have a horrible public API because the approach is fundamentally flawed. And that's before I even get into how it solves those problems. Now is it a bad thing it exists? No, obviously not. I'm glad it does, but we can learn what not to do from it as well.
- stevenwiles 10y agoWho are you? Why do you think you can speak with such authority?