News for hackers. Stuff that matters.
Re:Webpack 2.2 – Release Candidate by sergiotapia on Wednesday December 14, 2016 @07:02PM (#13180986)
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.

Re:Webpack 2.2 – Release Candidate by thelarkinn on Wednesday December 14, 2016 @07:24PM (#13181117)
Totally understand, now that webpack 2 is almost out the door, this is one of our top 5 overhauls we want to make.

"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.

Re:Webpack 2.2 – Release Candidate by ch4s3 on Wednesday December 14, 2016 @09:39PM (#13181923)
I love how you turn up immediately whenever someone mentions webpack!
Re:Webpack 2.2 – Release Candidate by thelarkinn on Wednesday December 14, 2016 @10:07PM (#13182060)
Well, as one of the maintainers besides working on core, and loaders/plugins, my role is to rep the voice of all of you to the core team, and also the other way around. Just here to help :)
Re:Webpack 2.2 – Release Candidate by ch4s3 on Thursday December 15, 2016 @07:51AM (#13184218)
You're doing a great job! Keep it up!
Re:Webpack 2.2 – Release Candidate by bpicolo on Wednesday December 14, 2016 @09:14PM (#13181774)
An alternative is a command line tool that could combine bits:

webpack-make --scss --hot-middleware --blah

or something, potentially?

Re:Webpack 2.2 – Release Candidate by thelarkinn on Wednesday December 14, 2016 @09:38PM (#13181916)
Do I have a github issue for you!!!! This is a feature tons of people ask for all the time so this week I officially marked it as RFC. https://github.com/webpack/webpack/issues/3466

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!!!

Re:Webpack 2.2 – Release Candidate by bpicolo on Thursday December 15, 2016 @08:15AM (#13184338)
Hah, nice. Sounds like you guys are pretty on top of things :) Afraid I'm not nearly caught up on webpack best practices to take a good whack at it, hah
Re:Webpack 2.2 – Release Candidate by mtrpcic on Wednesday December 14, 2016 @07:18PM (#13181091)
I solved this by keeping my Webpack build process in it's own repository, with a JSON file that dictates entry and exit points for builds. When doing a new frontend project, I use git submodules to import my build pipeline and just change a few variables and I'm set.
Re:Webpack 2.2 – Release Candidate by matallo on Thursday December 15, 2016 @04:46PM (#13188760)
This sounds a lot like Grunt.
Re:Webpack 2.2 – Release Candidate by emmelaich on Wednesday December 14, 2016 @10:06PM (#13182058)
> Smart defaults, allow configurations

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.