Webpack v4

[mikecx]

Didn't see another issue in the search for it but with Webpack v4 on the horizon and potentially being a stable release in about a month, is there work being done to update webpacker? The promise of less configuration, better build speeds, and smaller builds already has me excited.

[gauravtiwari]

@mikecx Thanks - yep once stable version is released.

[renchap]

Webpack v4 is now released: https://github.com/webpack/webpack/releases/tag/v4.0.0

Do you already have a defined plan to switch to it? It brings a whole lot of goodness.

[guilleiguaran]

@renchap there is any upgrade guide for Webpack 3 -> 4?

[renchap]

The migration guide is not yet published (webpack/webpack.js.org#1706).

The one for the alpha version is mostly up-to-date and should be fine: webpack/webpack#6357 (at the end of the top post)

Other useful links:

• Announcement: https://medium.com/webpack/webpack-4-released-today-6cdb994702d4
• Release notes: https://github.com/webpack/webpack/releases/tag/v4.0.0
• Migration guide for plugin and loaders authors: https://medium.com/webpack/webpack-4-migration-guide-for-plugins-loaders-20a79b927202

[rhazegh]

Looking forward to using webpack 4.0.

Hopefully it will help with lengthy build times on heroku.

[dbalatero]

@gauravtiwari do you need assistance with getting webpack v4 working? I'd be glad to help if so.

[gauravtiwari]

Thanks @dbalatero 🍫

I was thinking to do some groundwork (#1304 ) first before making an upgrade to v4. Also, noticed one of the plugins we use i.e. manifest plugin is still in RC. Would be great if you could help with some reviewing later :)

[renchap]

I can also help if needed (testing or implementing). But we need to coordinate to not do the work twice :)

[gauravtiwari]

Just published a pre-version with initial Webpack 4.0 support:

To try out:

gem 'webpacker', '>= 4.0.x'

yarn add @rails/webpacker

[faceyspacey]

@gauravtiwari awesome!! Gonna try it out now.

[adaam2]

Even after upgrading @rails/webpacker, I was still running into this problem. However there is another solution to fix this issue, which is by using resolutions to ensure that the webpacker version of extract-text-webpack-plugin is the new webpack v4 one:

"resolutions": {
    "@rails/webpacker/extract-text-webpack-plugin": "^4.0.0-beta.0"
  }