# Status of Webpack 5 support

**URL:** <https://discourse.aurelia.io/t/status-of-webpack-5-support/3969>\
**Category:** vNext\
**Created:** [January 8, 2021, 2:10pm UTC](https://discourse.aurelia.io/t/status-of-webpack-5-support/3969 "2021-01-08T14:10:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![graycrow](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/graycrow/32/323_2.png) [@graycrow](https://discourse.aurelia.io/u/graycrow)\
**Post date:** [January 8, 2021, 2:10pm UTC](https://discourse.aurelia.io/t/status-of-webpack-5-support/3969/1 "2021-01-08T14:10:43Z")

</div>

As of now, aurelia-webpack-plugin has no support for the current version of Webpack, v5.x. [Here is the github issue](https://github.com/aurelia/webpack-plugin/issues/166) tracking this problem, but there hasn’t been any activity there lately. So, are we waiting for Aurelia 2 release to support Webpack 5 (by design)? I think that supporting the current version of such a large part of the web toolkit is very important for the popularity of Aurelia.

---

<div class="post-metadata">

**Author:** ![huochunpeng](https://avatars.discourse-cdn.com/v4/letter/h/49beb7/32.png) [@huochunpeng](https://discourse.aurelia.io/u/huochunpeng)\
**Post date:** [January 8, 2021, 10:51pm UTC](https://discourse.aurelia.io/t/status-of-webpack-5-support/3969/2 "2021-01-08T22:51:02Z")

</div>

Aurelia 2 skeletons have been upgrade to webpack5.

---

<div class="post-metadata">

**Author:** ![ghiscoding](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/ghiscoding/32/1199_2.png) [@ghiscoding](https://discourse.aurelia.io/u/ghiscoding)\
**Post date:** [January 8, 2021, 11:26pm UTC](https://discourse.aurelia.io/t/status-of-webpack-5-support/3969/3 "2021-01-08T23:26:25Z")

</div>

I think the question is more around “_Will Au1 and `aurelia-webpack-plugin` be upgraded to WebPack 5 or will it be only Au2 that support WebPack 5?_”… and I’m also curious to know even if it’s not a deal breaker for me.

---

<div class="post-metadata">

**Author:** ![elitemike](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/elitemike/32/690_2.png) [@elitemike](https://discourse.aurelia.io/u/elitemike)\
**Post date:** [January 26, 2021, 4:19pm UTC](https://discourse.aurelia.io/t/status-of-webpack-5-support/3969/4 "2021-01-26T16:19:32Z")

</div>

I’m in the same boat. I won’t necessarily change, but if there are improvements that are drastic enough I will. I’m still hoping for a clean AU2 conversion of my project

---

<div class="post-metadata">

**Author:** ![Souldrinker](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/souldrinker/32/1956_2.png) [@Souldrinker](https://discourse.aurelia.io/u/Souldrinker)\
**Post date:** [February 3, 2021, 9:19am UTC](https://discourse.aurelia.io/t/status-of-webpack-5-support/3969/5 "2021-02-03T09:19:27Z")

</div>

Yes, even though as the others mention it’s no real show-stopper it’s still a bit annoying with the list of packages growing by the day when checking for outdated npm packages.

Just in the last 24 hours both expose-loader and postcss-loader released new versions that dropped webpack 4 support and adds to the growing list.

Also an npm audit shows that several vulnerabilities (although low) will be fixed by upgrading webpack to 5.x.

Sure Aurelia 2 looks nice from what I’ve seen so far and I jumped on the Aurelia train already in pre-alpha (from Durandal) which worked great, but this time I’m not so sure I dare to upgrade to an alpha version since the applications built with Aurelia1 here are now quite widely used, so I don’t want to take to risks when upgrading, so it would be nice if somebody looked into upgrading also AU1 to support Webpack 5 since I suppose a “stable” au2 is quite a bit away still.