Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
TL;DR: release planned for 2020-10-10
After nearly 1 year of beta testing and about 2 years of development we feel that it's time to release webpack 5 soon. As promised we do announce the release at least one month earlier to allow the ecosystem to catch up. To support that we
We will use the time until the release to:
This is works out great we release webpack 5 at 2020-10-10 because it's a cool date.
Note that while we consider webpack 5 as pretty stable, there are probably still many bugs and problems. Some are expected breaking changes, some are bugs that we missed. If you have problems upgrading make sure to read the migration guide and changelog where we places some hints how to fix these problems and/or why we did some of the breaking changes. If you still run into problems, it might be a bug or something is missing in the migration guide/changelog, please report an issue.
Note that some of the experimental features are still incomplete. They are excluded from SemVer for webpack and we continue to develop them...
Note that minor bugs won't prevent us from releasing. The release is more about finishing breaking changes then about a super stable release. We will release minor/patch version very often to address bugs and add more feature (as we have done with webpack 4).
As for me, webpack 5 became super-fast against its 4 version. Built-in cache works perfectly) And it wasn't to hard to switch from webpack 4 to webpack 5!
There are some issues, how to migrate my own loaders and plugins, but there are just some warnings, and it is nice, cause you (webpack team) have made so many cool features, and there is no serious problems with version switching.
Thanks for the heads up ( jantimon/html-webpack-plugin#1514 )
Is there any api which returns the calculated publicPath?