🎉 webpack 2.2: The Final Release 🎉
Last month we shipped our first Release Candidate for webpack 2.2. Since then, we’ve been hard at work fixing any bugs that you reported. Not only that, but we’ve merged over 220 pull requests from the community in helping us refactor our core library to ES2015 (yes, this means our minimum supported NodeJS version is now 4.3).
On behalf of the entire webpack team, I’m proud to announce that webpack 2.2.0 is officially in final release!! 🎉 (And final doesn’t mean that we stop working on it.)
💻 How to download? 🖥
We will leave the final release on npm published under the
beta tag for the first week. This means you can run the following to download webpack 2: (or first-time users can checkout our “Getting Started” guide)
npm install webpack@beta
After that first-week grace period is over, we will move it to the
latest tag. This means you will be able to run
npm install webpack to install final into your project.
npm install webpack
If you are migrating from webpack 1, please see our step-by-step migration guide to walk you through the upgrade process.
For information on specific changes between webpack 2.2.0-RC and 2.2.0, check out our releases page.
✈️ VIP office hours and on-site training available ✈️
Looking to have additional support with a member of the webpack core team? Interested in having a webpack maintainer come on-site to hold a workshop, presentation, or discussion? We have a few great offerings through our open collective:
- VIP office hours: We are starting office hours and sponsors with a subscription of at least $500 per month will have access to sign up for them. We can help troubleshoot, teach, or answer whatever webpack or open source related questions you have.
- On-site visit: On top of VIP hours, for sponsors of $2000/month and up, we will have a webpack maintainer fly to your office and spend the day, training, teaching, advising, and getting to know your team.
We are still working the details out for these offerings. Note that there are only limited amounts available. For questions or information, please email us at email@example.com.
📝 What’s next? 📝
As no release is perfect, we’ll focus on resolving the most immediate issues that arise. In addition, we’ll also continue to improve our new documentation site.
After that, there are so many things we could do, so we don’t want to decide this alone. Therefore, we set up a voting tool where everyone, especially backers, can decide on the next thing we will tackle. Choose wisely, with great power comes great responsibility.
To vote, you need to login with your GitHub account. Donations for Open Collective are regularly synced. Your Open Collective email address needs to be added to your GitHub account and you need to re-login after that. It can take a few days until your donation is available.
Even as we speak, there is a battle between Typescript Tree Shaking and Scope Hoisting. Both are size/performance optimizations. Vote!
🙇 Thank you. Again. 🙇
To all of those involved on our contributor team, the core team, loader and plugin authors, those who submitted their first time commits, or assisted with troubleshooting: we cannot thank you enough. This product is for you and helped shaped by you.
No time to help contribute? Want to give back in other ways? Become a Backer or Sponsor to webpack by donating to our open collective. Open Collective not only helps support the Core Team, but also supports contributors who have spent significant time improving our organization on their free time! ❤