-
Notifications
You must be signed in to change notification settings - Fork 144
Update to Webpack v5 #8326
Comments
Thanks @chihsuan , I was just about to create this same issue, and came across yours! Just noting here that this was attempted shortly after Webpack 5 was released, but aborted due to the lack of support from various plugins. It's definitely time to revisit, as this is also a blocker for my css-in-js efforts. |
Thanks for sharing this @joelclimbsthings ! I think our next step will be to investigate whether all the plugins now support webpack 5. From the previous issue:
|
Agreed @adrianduffell , I actually started looking at this the other day. This was a fairly cursory survey, but since it looks like you may pull this into your sprint I'll share my (perhaps incomplete) findings here: copy-webpack-plugin eslint-import-resolver-webpack fork-ts-checker-webpack-plugin moment-timezone-data-webpack-plugin terser-webpack-plugin webpack-rtl-plugin @woocommerce/dependency-extraction-webpack-plugin @wordpress/custom-templated-path-webpack-plugin @automattic/mini-css-extract-plugin-with-rtl webpack-bundle-analyzer webpack-fix-style-only-entries |
Awesome, thanks @joelclimbsthings ! |
Recently I tried to build with
[email protected]
but encounter an error due to optional chaining operators. I found it's a webpack issue that Webpack v4 doesn't support it.I've updated the
exclude
option of babel-loader as a webpack4 solution in this commit c986711.But I think we should consider updating to Webpack v5.
The text was updated successfully, but these errors were encountered: