Am I the only one who wishes Starter Kits come up with a tutorial on how to build them up from scratch?
It would be extremely helpful to document why the configs are the way they are. See this long twitter thread on what I discovered by ejecting create-react-app configs: https://twitter.com/dmitriid/status/908677755046449154
Some highlights:
- Because of course you need to write your own webpack message formatter
- Because of course you have to manually set up listeners for SIGINT and SIGTERM to tear down the dev server
- Because of course you have to manually write a module resolution helper that basically replicates node's resolution mechanism
- Because of course dev server spits tons of crap, so you silence it and manually write a custom message emitter
- Because of course you have to write your own error overlay for a dev server
- Because of course you have to pretend your structured folders are flat for some tools, and you have to write manual overrides
etc. etc. etc.
Simply because some poor soul spent countless hours and never documenting the journey we have the crappy tools that we have. All these horrendously inane configs should not be hidden behind a wrapper, but called out, created as issues and fixed.
Because it took the webpack team several years to even acknowledge that simplified configs with default values are a good thing. I mean, in 2017 they said that webpack will always be crap because it can't provide defaults because "that's how Javascript is": https://twitter.com/dmitriid/status/920542261020160000
etc. etc. etc. etc.