Update the description of the webpack runtime chunk #323
Conversation
|
Next question is whether we should rename the output file from manifest.js to runtime.js (matching the default name used by Webpack 4 when enabling such feature). This would reduce the confusion between manifest.js (the runtime file) and manifest.json (the manifest). But that would be a BC break (as projects have to load this runtime file in their HTML). |
Lyrkan
left a comment
Lyrkan
left a comment
There was a problem hiding this comment.
Not sure about modifying the name of that file yet.
I think it'd be easier to justify that change after switching to Webpack 4 which will probably also introduce some other BC breaks related to common chunks.
|
yeah, delaying this until the Webpack 4 migration might be fine. |
|
It's so confusing, I even typo'ed it in my notes :p. And yes, I think we should rename this - runtime.js is much more clear. It's already done on the Webpack 4 branch. |
This PR was merged into the master branch. Discussion ---------- Update the description of the webpack runtime chunk What gets extracted in this chunk is not the manifest (which creates confusion with the webpack manifest which is a JSON file used by the backend code, i.e. the Symfony asset component); it is the webpack runtime. This runtime indeed includes some information also present in the manifest (it contains the mapping for all dynamic chunks), but that's not all of it. Commits ------- 992845e Update the description of the webpack runtime chunk
What gets extracted in this chunk is not the manifest (which creates confusion with the webpack manifest which is a JSON file used by the backend code, i.e. the Symfony asset component); it is the webpack runtime.
This runtime indeed includes some information also present in the manifest (it contains the mapping for all dynamic chunks), but that's not all of it.