Scripts: Use the latest version of webpack for build and start commands

[gziolo]

Description

This PR upgrades the version of webpack used in @wordpress/scripts.

There should be no changes in how npm run dev and npm run build work in Gutenberg.

In addition, I updated the list of dependencies for @wordpress/scripts to use ranges for consistency.

[gziolo]

cc @jsnajdr @simison

[simison]

Failed JavaScript unit tests just look like you should update some snaps?

[gziolo]

Failed JavaScript unit tests just look like you should update some snaps?

I will fix it soon. It looks like webpack produces a different hash for files, interesting. @sirreal, any idea what could happen?

[gziolo]

Updated with 29a3e3e. Travis seems to be much happier now 🎉

[gziolo]

@youknowriad - this is another one to include in the npm release process since we use a super out of date version of webpack.

[jsnajdr]

It looks like webpack produces a different hash for files, interesting.

That hash includes also the webpack runtime code. If something in the code that loads and executes the webpack chunks and modules changes, the bundle's hash will change, too.

Here's one example of a simple change in the runtime code that happened between 4.8.3 and 4.41.0. It changes head references to document.head: webpack/webpack@6f5c5ef33

[simison]

CI build obviously succeeds and I appreciate the version range change. 👍

Does version range change need a major Semver update?

[gziolo]

Does version range change need a major Semver update?

webpack follows sem ver as far as we can tell, so it's safe to assume there are only enhancements added given it is still v4.x.

[gziolo]

@youknowriad - another one to include in the next npm release.