what is the timeline for the release of webpack 2? #1545

Closed
benmonro opened this Issue Oct 23, 2015 · 61 comments

Projects

None yet
@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
Member
sokra commented Oct 26, 2015

Soon...

@joshmanders

@sokra's reaction:

@sokra
Member
sokra commented Oct 26, 2015

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
igl commented Oct 26, 2015

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?

@andrew-w-ross

@sokra Thanks, what would you like help with?

@sokra
Member
sokra commented Oct 29, 2015

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.

@bebraw bebraw added question webpack-2 and removed question labels Nov 14, 2015
@okian
okian commented May 6, 2016

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

@Delagen
Delagen commented May 6, 2016

@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
Member
sokra commented May 6, 2016

ASAP... :-O

@Delagen
Delagen commented May 7, 2016

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
bbottema commented May 17, 2016 edited

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.

@8balloon

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

@sokra
Member
sokra commented May 19, 2016

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
Member

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

@tbekolay tbekolay referenced this issue in nengo/nengo_gui Jul 11, 2016
Merged

Refactor frontend pt. 1 #805

@graingert

@igl jsnext:main

@pmorch
pmorch commented Aug 31, 2016

We're about to embark on Webpack, and can see that Webpack 2 is "any day now". In the meantime, we'll use Webpack 1 of course.

I'm assuming that with a new major version number will come breaking changes.

Does the team already know what will break in a version 1 => 2 migration? Are there any hints as to any Webpack 1 idioms or approaches one should either employ or avoid because they'll help/give problems later with Webpack 2?

@cecilemuller
cecilemuller commented Aug 31, 2016 edited

This is not an exhaustive list, but if it helps, I recently upgraded one of my boilerplates to webpack2, so what I had to change was just:

  • the version number of packages webpack, webpack-dev-server and extract-text-webpack-plugin
  • replaced custom commandline flags by --env parameters

So far, the transition was pretty smooth 😄

@bholloway

@pmorch It does depend on the plugins/loaders you intend to use.

I maintain a couple and have had feedback that they are not Webpack 2 compatible. In my new job I am not dog-fooding so I've not yet looked into the migration process.

@mkscrg
mkscrg commented Sep 15, 2016

Is there an updated timeline for a stable v2 release? Alternatively, is there a list of issues/bugs for would-be contributors to jump on?

Also +1 for crowdfunding webpack—it's become an important piece of infrastructure!

@ChrisCinelli
ChrisCinelli commented Oct 21, 2016 edited

This coming Sunday is the first birthday of this issue =)
@sokra commented "soon..." on Oct 26, 2015.

But it looks like there are still some big issues outstanding now that we are at beta 25.

I think some people early this year were thinking that we were close to stable release.
I saw that some plugins were releasing a new version for webpack 2. I saw some boilerplates rushing to upgrade to webpack 2. I started a project with a boilerplate that used v2. But as time went by, people realized that we may still far from a stable v2 .

So getting pragmatic:

I am having some problems with dependencies every once in a while. My hope to see everything working soon are pretty low. But before I spend a few days on this, I want to ask it.

Should I wait just a little more or should I downgrade to v1 in the meanwhile?

@TheLarkInn
Member

Omg, you guys are so funny. Okay, so we stuck to our word posted on various mediums that when our doc milestone is completed.

So we are at 84% and there is a little bit of work left, but the more help we have from you in the effort, the faster you get webpack v2.

@TheLarkInn
Member

But it looks like there are still some big issues outstanding now that we are at beta 25.

What issues were you referring to? Besides one change, (in regards to adding import() for the loader spec).

@corysimmons
  1. Just use Webpack 2 right now. Who cares if it's perfect? It works and you'll know if it breaks something. I've heard from plenty of people they've been using it for a while.
  2. Just super hyped about dead code elimination? Use Rollup or Closure Compiler?

It's not like you guys won't see "WEBPACK 2 LAUCNH D OMG!!!" on every site for a week when it finally lands.

Lock thread and have pizza party instead. :\

@bbottema

@corysimmons Some of us are actually professionals. I'm not going to push our enterprise projects with 20 developers into "yet another tool" that might go extinct the next month. Switching to Webpack 1 already was dicey enough. I just got our devs used to it.

What I need is an actively developed tool with lots of documentation and an active community. Webpack 2 isn't any of that.

@pastelsky

@bbottema
Your being an enterprise user matters very little in the context of an open source project. You aren't paying for these tools and hence it's silly to demand hard ETA'S and enterprise level documentation.
Why don't you and your enterprise try contributing to the blockers instead?

@bbottema
bbottema commented Oct 23, 2016 edited

@pastelsky wow, are you seriously suggesting enterprise parties only have rights to rely on paid libraries "unless they contribute"? How do you think Angularjs got so much traction, because it was massively adopted in the enterprise sector. Excluding large groups of users from open source dialogs this way is not the way forward. That is one way to secure a library's demise.

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.

@fab1an
fab1an commented Oct 23, 2016 edited

Okay, the way I see it, please correct me if I'm wrong, is that many people would like to contribute to get webpack 2 finished.

The problem seems to be that the missing part is mainly documentation, which is harder to get into than actual code. Because you need to fully understand what the code does to be able to document it, am I right?

Are there areas other than documentation that need polishing or testing?

@fab1an
fab1an commented Oct 23, 2016

@bbottema I would stay with webpack 1 for now. There's babel-minify (https://babeljs.io/blog/2016/08/30/babili) around the corner as well, which might provide another way towards treeshaking and the minification of ES2015.

@TheLarkInn
Member

What I need is an actively developed tool with lots of documentation and an active community. Webpack 2 isn't any of that.

@bottema we have almost finished our MVP docs milestone. webpack.js.org is the newest page and we have our migration guide under the how to section.

Is there anything else you are referring to that you would like to see?

@corysimmons

@TheLarkInn It might be a good idea to slap that webpack.js.org link on the top of Webpack's README with some label like "Looking for Webpack 2 (still in beta) documentation?"

@joshmanders

@bbottema

into "yet another tool" that might go extinct the next month.

Webpack has proven itself that it won't "go extinct the next month." So that argument is moot.

What I need is an actively developed tool with lots of documentation and an active community. Webpack 2 isn't any of that.

Yeah man, webpack is not an active community and no documentation. 🙄

Excluding merges, 10 authors have pushed 14 commits to master and 23 commits to all branches. On master, 61 files have changed and there have been 6,591 additions and 1,758 deletions.

Get off your horse, this attitude is what drives great open source developers away, your entitlement is not needed or wanted here. There is no rush for webpack 2, if you think there is, by all means, dig in and contribute, otherwise keep your trap shut.

@fab1an
fab1an commented Oct 23, 2016

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
Member

@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
joshmanders commented Oct 23, 2016 edited

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
Member

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

@bbottema
bbottema commented Oct 23, 2016 edited

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
Member

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
Member

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

@bbottema
bbottema commented Oct 23, 2016 edited

Please close this down. I've had enough.

@TheLarkInn
Member

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

@turadg
turadg commented Oct 23, 2016 edited

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
Member
sokra commented Oct 23, 2016
  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
ChrisCinelli commented Oct 23, 2016 edited

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:
    search weppack 2 on google
    This is what the first result look like:
    webpack roadmap
    And this is the doc:
    todo webpack 2
    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 ?
@Luchillo

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

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
Member
sokra commented Dec 1, 2016

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... 🎄 🎆

@valscion valscion referenced this issue in railsware/js-routes Dec 11, 2016
Closed

Switch from CoffeeScript to modular ES2015 #215

@bebraw
Member
bebraw commented Dec 31, 2016

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

@bebraw bebraw closed this Dec 31, 2016
@dwqs dwqs referenced this issue in dwqs/blog Jan 22, 2017
Open

[译]Webpack 2 快速入门 #46

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment