You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Took me a bit to figure out what this is about, but I guess it's saying that they have a script which goes over each file in asset manifest (e.g. to add a <script> for it to a custom HTML page template), but runtime chunk is not there.
I wonder how we could handle it. I guess folks who use asset manifest (e.g. Django integrations and similar) won't read the runtime chunk from our HTML. So it'll be broken anyway.
Should we both emit runtime chunks and inline it? Normally it gets unused but folks who read the manifest get a separate script.
The text was updated successfully, but these errors were encountered:
gaearon
changed the title
Non-existent files (e.g. runtime chunk) shouldn't appear in asset manifest
Runtime chunk inlining and asset manifest
Sep 29, 2018
Took me a bit to figure out what this is about, but I guess it's saying that they have a script which goes over each file in asset manifest (e.g. to add a
<script>
for it to a custom HTML page template), but runtime chunk is not there.I wonder how we could handle it. I guess folks who use asset manifest (e.g. Django integrations and similar) won't read the runtime chunk from our HTML. So it'll be broken anyway.
Should we both emit runtime chunks and inline it? Normally it gets unused but folks who read the manifest get a separate script.
The text was updated successfully, but these errors were encountered: