-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webpack 4 Documentation #1897
Comments
No, documentation for webpack 4 it is not ready and there is not release date. 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 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:
|
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. |
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.
The text was updated successfully, but these errors were encountered: