Is it just me or is there no documentation yet for Webpack 4? I am trying to read more about this "splitChunks" thing but I can't find crap on the website. Hell the website shows version 4.1.1 but still says to use CommonsChunkPlugin
This issue was moved from webpack/webpack#6711 by @ooflorent. Original issue was by @bannostookaylo.
No, documentation for webpack 4 it is not ready and there is not release date.
You can read more about new splitChunks in our Medium publication https://medium.com/webpack, which is linked from everypage in our website via Blog link at the top of the page.
You can follow webpack 4 documentation progress at #1856.
Website version is a badge that shows latest release, it doesn't indicate website version.
-1 @montogeek
The documentation should be ready _before_ the release is added to NPM for people to consume. Especially if it is a major version upgrade (i.e. breaking backwards compatibility).
On top of that, you could have at least linked the relevant Medium articles:
I concur: The documentation should be finished (or at least be ready in a preview form) once the new version goes live. To make matters worse: On the webpage there is a big indicator stating "webpack v4.1.1" which indicates (at least to me) that the documentation I am currently reading is for exactly that version.
I think this should be reopened until the documentation is ready, as a tracking ticket (or identify another ticket where progress of Webpack 4's documentation is tracked). I noticed webpack/webpack#6711 was moved to webpack.org.js, but it does not specify _where_.
Is this issue, and also from my first comment:
You can follow webpack 4 documentation progress at #1856.
This should have been a high priority item. What's the point in releasing minor versions if the general populace isn't even moving to Webpack 4 (due to lack of docs)?
Worse, the existing docs are misleading - they should be labeled as v3 to avoid the confusion.
Most helpful comment
-1 @montogeek
The documentation should be ready _before_ the release is added to NPM for people to consume. Especially if it is a major version upgrade (i.e. breaking backwards compatibility).
On top of that, you could have at least linked the relevant Medium articles:
splitChunks
Webpack 4 migration guide for plugins and loader
New import and CommonJS support