thelarkinn

At what cost :-D

From the webpack team to Devon:

Thank you so much for this work! Not only are we happy to see a real contender in the bundling space, but also look forward to not only work together, but also learn from parcel in ways we can help make webpack more flexible and easy to use for those who want "zero configuration".

Welcome to the bundler family!

Sean webpack team

Thank you HN-landia for all the love and support of webpack. We look forward to a lot of candid/helpful feedback. You can always find us on twitter or GitHub. (@TheLarkInn)

Hope to see as many hands on this alpha preview as possible!!

- webpack team

Native modules are still pretty slow. So much that we as an oss org are working with browsers to help them find ways to make them faster. Although native modules will be nice, we still believe that bundlers are still needed to ship the fastest most optimized code

The tool aims to be agnostic to work flow it's a trade-off to be generic in our case. We realize it too.

It's more then nice words. It's showing you listen, it's empathizing, it's putting yourself in that persons shoes. To fix things like usability we have a lot of long work ahead of us and we want to do so.

I don't consider that person a hater etc. I think maybe the transcript of my talk didn't really mean to couple that statement with that slide etc.

Hey maybe you are victim of this and I missed out!

I don't consider this a game, I take it pretty seriously to help others. However, I am human like many others and as of late I've been a bit caught up with family. If this happened to you then by all means I can own it and apologize. Otherwise shoot me a DM if you really need help and if I can't help I'll find someone who can

Hi there! Sean from webpack (@TheLarkInn).

I know that many of the packages you have listed are not immediate but transient dependencies.

That being said, we still would welcome at any time improvements to transient or dependent packages that we use in webpack, and consider this a really really valuable contributions up stream to many projects!

Heh it was trending two days on reddit/r/javascript but is hit or miss.

He intentionally left the project to protect the IP of Inferno from falling into the same patent'y business is what I heard.

VS and EdgeDevTools use InfernoJS I believe. Another VDOM implementation.

I can understand your point. But here is our belief at webpack: The community owns us, sponsors and backers are our shareholders, yet at the same time, they are all candidates to expense and fund the time they sacrifice contributing to our community. Until Sokra (Tobias Koppers), went full time (thanks to our continued growth in support) we have expensed more of this sponsor and backers funds to our external contributers than to ourselves as the core team.

Our community is growing so rapidly that there is no reason why any person shouldn't be able to receive the same recognition and appreciation for their work, than we should as a core team.

I have been in charge of finding sponsors, backers, and partners for our organization and I always focus on this first: don't for funds but instead relationships, opportunities, and ways we can use their contributions (whether it is man hours or funds), as a vessel to mutually benefit those individuals through increased learning, mentorship, marketing value, support, and more.

An example of this would be our application to the MOSS Grant board to support an initiative dear to Mozilla to add first-class module support for WebAssembly. This not only allows us to potentially be awarded over 100k in funding, but also helping Mozilla support their initiatives, and finally, putting a feature such as WebAssembly in the hands of Developers in an accessible and pragmatic way.

As a project when you focus on money and who is sponsoring your project, you lose sight of the true beauty of open source.

In the end the only thing that matters to us is that you give a shit about our mission and want to find any way to give back to the organization, contributors, and users.

Sure! webpack.js.org/concepts

Ironically the biggest challenge is involved with connecting a very declarative under the hood plugin architecture, to a more imperitive fluid configuration for users. We would love all the great ideas we can get!

Thanks whoever posted this article!!! On behalf of the webpack core team, we thank everyone who's been using webpack 2 since beta, we are at the finish line for getting final release. :) stay tuned

Awesome post!!! I'll reach out to our awesome-webpack companion repo and add this repo. Besides that, on behalf of the webpack core team, feel free and reach out if you have any other questions or want to get involved.

We even have a new docs page where hopefully _most_ of the things on this document are (if not should be) covered.

webpack.js.org webpack.js.org/concepts

~Sean + webpack Team

Sorry to hear that was your experience, but also glad to hear you found a solution that works. If you do come back to trying webpack, we're happy to help get you up and running. Feel free to reach out on twitter or github @TheLarkInn

We have a plugin built around the research on HTTP/2 and web perf (which based on the data so far points to bundling still yielding the optimal results) called AgressiveSplittingPlugin.

It's designed to allow you to specify a max and min file size and webpack(2) will create x bundles of those size up to a certain number (if specifies). The advantages are now you are drastically increasing the delivery of your js and other assets but still bundled for opt.

Sokra (Tobias) wrote an article about this research if you are interested!!

https://medium.com/webpack/webpack-http-2-7083ec3f3ce6#.5yca...

Also to see an example of the API usage you can visit our core repo under examples where we explain the trade offs (compression vs cacheability):

https://github.com/webpack/webpack/tree/master/examples/http...

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 :)

Check the actual article and you'll see the v1-v2 migration link embedded into the post!!!

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

We are really excited to work with Rich Harris on adding scope inlining, (Rollup'y) features. We were waiting to release 2 first :-D

Hey sorry this was your first (or many) experience(s). If I can be of any help, I'd recommend checking out our Concepts section which I authored for first-time users and those trying to understand the overall principles of loaders/plugins.

webpack.js.org/concepts

Also, if you find a plugin or a loader who is struggling to support or catch up, just drop us a message on github or tweet me at @thelarkinn, and myself or one of the other maintainers will offer to help or take over the plugin. We have a whole contrib team dedicated to helping maintain our core org loaders and we are always wanting to keep the ecosystem strong and up to date.

Well thank you for always being candid and honest with your feedback to us. We really rely on feedback from the community who is ultimately in charge of the direction of this incredibly humbling project.

This goes to more than just you, but please always feel welcome to reach out.

No that was handwritten by Tobias the original author and I shared it on Twitter a few weeks back. We do have a lot of abstraction and complexity internally. But we like the direction and way it has allowed us to pivot toward and away new/old features.

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.

Thank you guys for the positive feed back. If you find anything quirky or just want to get involved, feel free and drop us a github issue. ️

There is potentially a plugin that might work for you but an RFC on our core repo would be worth the time. Check out hard-source-webpack-plugin and see if that helps you.

Coming from a no-design-ux background, I never considered this and it would be a perfect issue on our github. Would you be interested in creating it? github.com/webpack/webpack.js.org/issues/new