what is the timeline for the release of webpack 2?

[benmonro]

I'm looking forward to using this feature: https://github.com/webpack/webpack/tree/webpack-2/examples/harmony-unused

but since this is in the webpack 2 branch, i'm curious as to when this will be released? what is the timeline?

Thanks
Ben

[joshmanders]

👍

[sokra]

Soon...

[joshmanders]

@sokra's reaction:

[sokra]

yeah.

I don't have a timeline yet. I depends on the available time for webpack.

[joshmanders]

One of my favorite new features, don't feel pressured, I am anxious for it. Thanks for all the hard work you do.

[igl]

Recently saw this in http://rollupjs.org/. This kind of dead-code removal coming to webpack is awesome!

But where do we get our uncompiled es6 libraries?
npm won't have it until es6-module support is in v8 for a few versions. Nodes new LTS strategy does not help there.
JSPM focuses on browsers..
I guess that only leaves: sokra needs to hack something together there too ;)

[andrew-w-ross]

Is there a roadmap for what needs to be completed before 2 can come out?

[sokra]

Here is a list of my notes: https://docs.google.com/document/d/1tRc0MzvRdGK7EbG2LRW8vSyoxKhR_EvRUz3AQRyFZso/edit?usp=sharing

[andrew-w-ross]

@sokra Thanks, what would you like help with?

[sokra]

You could prepare a PR to the webpack-dev-server which removes the iframe mode and only uses the inline mode. Merge it with the PR about webworkers.

[okian]

@sokra Any update about this topic? why webpack doesn't have blog?

[Delagen]

@moostad I cannot get it work with the base loader as source-map-loader. So it is unusable in this state. 1.13 works fine, but es6 is needed ASAP

[sokra]

ASAP... :-O

[Delagen]

I was trying to use beta, but it not usable in this state, alpha versions of another products more usable

[kristian-puccio]

I mean seriously given how much we are paying for this, I would expect
better!

note: sarcasm

On 8 May 2016 at 03:43, Vohmyanin Sergey Vasilevich <
notifications@github.com> wrote:

I was trying to use beta, but it not usable in this state, alpha versions
of another products more usable

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#1545 (comment)

[andrew-w-ross]

@kristian-puccio Yeah when I pay nothing for something I expect results.

[bbottema]

I would probably pay if there was some kind of crowdfunding to get a new release done! If that's what it takes to give these devs more time on webpack (or attract freelancers), then sure why not.

[ethangclark]

@bbottema There's a link to tip on the repo page :)

[sokra]

There propably will be some crowdfunding in the near future. I need to work at least part time on webpack to cope with the demands...

[joshmanders]

Webpack is great, please let us know when and where we can donate, I have no issues helping you out, you've taken a crap ton of time off my work plate with this.

[brianblakely]

I'm a little surprised that Facebook hasn't gotten more deeply involved, considering how common it is for React and Webpack to be used together.

[KingScooty]

Is there an upgrade doc for upgrading to webpack2? Proxying, and React hot loading has completely broken on me, and i'm struggling to figure out why :(

[andreicek]

@sokra any updates on the crowdfunding funding?

[pastelsky]

It would be great to get sense of what's blocking webpack's transition from beta to stable.

We understand that its gone through a fundamental rewrite, and a lot of great effort has gone into the 13 beta revisions that have taken place in slighly less than a year now, but we are hoping for some transperancy leading to 2.0 release.

The roadmap docs don't seem to be updated any longer, and documentation for 2.0 is insufficient at best. It would be helpful if there was a short blog post / github post outlining a roadmap.

[matteocng]

@andreicek +1, crowdfunding v2 would be great!

[corysimmons]

https://youtu.be/nSipYY933eU?t=52

[fab1an]

Wow, I haven't seen such rude communication in a github-issue for quite some time. Could you please stop telling each other off?

[TheLarkInn]

@corysimmons we are actively working on having that done.

@joshmanders by all means I appreciate the support and statistics. Currently working for a Fortune 500 insurance company myself, I understand the Enterprise Architecture awareness that @bbottema is coming from and do not take it personally. (Although we are all professionals here and this is not the place to question otherwise.)

I would like to answer or reassure @bbottema if I can about any information or questions if he has them (therefore I have not locked the thread).

So I ask you all kindly please to not attack or question each other for whatever reason. Rather, let me help answer the questions that he has.

And nobody is demanding anything (are you trolling). All I did was voicing a thumbs up and suggesting a crowd funding might help move things along.
As I said earlier in this thread, I would personally gladly help pay for extra focused man hours if there was some kind of crowd funding going on. But no, I don't have the freedom nor the power to direct our own personel to external projects. I don't think that surprises anyone. It's not like we can't do it with Gulp instead. There's no real business case there other than making our developers happy and hopefully more productive.

In fact we just released and announced from our latest medium publication that we are now apart of open collective. This is a free and trackable way to donate to our causes: http://opencollective.com/webpack. I hope that answers that question @bbottema. We are always looking for sponsorship, etc.

If you would be willing to take the time to do so, I would strongly encourage you to look at our new doc page, and then please submit any github issues for where you believe documentation is lacking.

[joshmanders]

I apologize, it just bothers me when hard working people are giving their free time to make all our lives easier and better get bossed around and told what to do by entitled people. I don't care if you're enterprise or a solo developer. Nobody and I mean NOBODY has the right to talk with such a tone towards open source developers. We all should be grateful for the work you're doing for us.

I personally feel if they can speak that way towards others, then they should not be avoided being spoken back to that way.

[TheLarkInn]

I agree and we will leave it at that please and thank you.

[bbottema]

I'm not bossing around anyone nor demanding anything. Why the poisonous tone, guys?

I'm an open source developer myself, (check my history) so I know very well what it means to maintain an open source project. I'm also an external contractor with enterprise sized clients, so I also know how that angle plays out. Webpack 1 is awesome and I'm rooting for Webpack 2 and I wish to leave it at that, I have no need to wage some proxy war on behalf of enterprise or OS developers such as myself.

I'm sorry the discussion lead this way, but I feel I've been quite courteous. I'll keep quiet now.

[TheLarkInn]

Alright, again. Any more responses on this and non-webpack related issues I will close the thread. We all get our intentions were not to be malicious. Last warning

[TheLarkInn]

@bbottema Do you have any other questions in regards to webpack 2's release, and has it not been stated clearly?

[bbottema]

Please close this down. I've had enough.

[TheLarkInn]

Ill leave the issue open for anyone else who has questions. Thank you for the timely response.

[turadg]

Okay, so we stuck to our word posted on various mediums that when our doc milestone is completed.

It may help to update https://webpack.github.io/docs/roadmap.html to indicate that. When I search for "webpack 2", it's the first hit. And that pages says,

(for the most up to date version see https://docs.google.com/document/d/1tRc0MzvRdGK7EbG2LRW8vSyoxKhR_EvRUz3AQRyFZso/edit?pli=1)

That gives a very different answer. For example, implying a block on two open issues. Is that Google Doc authoritative anymore?

It might be helpful to answer these on an authoritative FAQ page:

1. When will Webpack 2.0 be released?
2. How can I help Webpack 2.0 to be released sooner?
3. What parts of Webpack 2.0 are lacking documentation?

[sokra]

1. We will announce it 1 week beforehand. This year. There are some critical issues left in the core and the documentation must reach a minimum quality. Some loaders need to be updated to use webpack 2 features and reflect webpack 2 changes in documentation (could be finished after the release).
2. easiest way is to help with the new documentation. It doesn't need to be a perfect contribution. We review the PRs and will do a review of the complete documentation before release.
3. https://github.com/webpack/webpack.js.org/projects/1 and https://github.com/webpack/webpack.js.org/issues or just try to read the documentation at https://webpack.js.org/ and check what's missing (create issue)

[ChrisCinelli]

Awesome! Thanks @sokra and @TheLarkInn for the updates.
I echo what was said here: #1545 (comment)

I think people could help with documentation, but they need to know that help is need and know how to do it.
Make sure that it is clear what the status is and what need to be done is the first step. A person should not have to go through a few google searches and read multiple issues on Github like this with about 50 or more comments.

My suggestions:

1. Establish a place that is the "source of truth" for Webpack 2 status. To me a page on https://github.com/webpack/webpack/wiki seems the easier place where people can keep things updated without too much overhead. This page can have direct links to drill down. For example: "How to help with Webpack 2", "I am the author of a loader or plugin, what do I need to do", etc.
2. Make sure that it is clear where the "source of truth" is and it is easy to find it. This is what I get from Google:
   
   This is what the first result look like:
   
   And this is the doc:
   
   I have not seen any update on these links for a while. The perception is that webpack 2 devopment is stuck.
   Can the roadmap and the google doc point to the same place where things are kept updated?
3. There is a huge dependency problem currently. If people do not fix the version in their package.json, any dependency on webpack plugins that are included with ^ or ~ starts breaking every now and then.
   I think there should be a clear guidance to help people and plugin authors to fix the dependency problems. The current situation does not help people to move toward v2.
   Having kept webpack-v2 in beta for one year with breaking changes from a beta version to the other did not help either. For a package author is not easy to specify the peer dependencies. It is also not easy for the end user to upgrade from a beta to another. If you add to the equation that a bunch of plugins authors do not have the time, do not know how or do not care to keep things updated, this ends up in a total mess.
   Can you guys adopt Semver ?

[luchillo17]

Hi @ChrisCinelli, i took a look at the roadmap and this is what it shown:

It says the new docs are in https://webpack.js.io, however the wiki says it should be https://webpack.js.org/, who should i let know about it to get it fixed? i banged my head to the wall a few times before taking a look to the wiki (thanks to your comment above).

[bjornstar]

The milestone looks cleaned out and things sound pretty stable.

Looking forward to the release of Webpack 2!

[sokra]

https://github.com/webpack/webpack/milestone/9

and we still want to review the docs

but we are nearly there. Expect a Release Candidate this year... 🎄 🎆

[bebraw]

We are running RCs now. Probably time to close this issue.