Smart defaults, allow configurations. That's the key.
I learned how to use Webpack but still think it sucks and it's incredibly complicated for what it does for 90% of use cases.
Smart defaults. -Then- let me configure if I need to.
I learned how to use Webpack but still think it sucks and it's incredibly complicated for what it does for 90% of use cases.
Smart defaults. -Then- let me configure if I need to.
"Can we make smarter defaults"
We support a lot of build targets and are agnostic to library and stack so it's going to be a challenge but with your help and the community I know we can get it done.
webpack-make --scss --hot-middleware --blah
or something, potentially?
Since the core team needs to focus on implementing more opt features like rollup and better top level minification, we left this for a chunk of our contribute team to help design and come up with. Help always wanted!!!
but also please have those discoverable.
I've come to hate the word default because people have a different idea of what it means.
Is it a site default, an app default, per-instance default ...?
Which one applies? Apps should document at runtime what the values are and where they come from.