Runtime.js not inlined in production (i.e. how to enable “emitHtml”)

tedw · May 31, 2022, 6:45pm

When using splitChunks() and runtime() it seems runtime.js isn’t being inlined automatically in my template. It appears this is the default behavior (see bud/extension.ts at b00e713905b351dcb4b4dcf827540dc81a919600 · roots/bud · GitHub) but I’m unclear how to change it. Any help would be much appreciated!

feature(entrypoints-webpack-plugin): options to emit as html

roots:next ← roots:entrypoints-html-emit

opened 01:00AM - 29 Dec 21 UTC

kellymears

+222 -50

## Type of change - MINOR: feature ## Dependencies added - none ## D…etails Can specify the `emitHtml` option to generate an html file with the `<script>`, `<style>` tags and the inlined runtime per entrypoint. Example: ```ts // ...webpack config plugins: [ // ... other plugins new EntrypointsWebpackPlugin({emitHtml: true}) ] ``` In the case of `@roots/bud-entrypoints` this looks like: ```ts bud.extensions.get('@roots/bud-entrypoints').setOption('emitHtml', true) ``` emits `app.html`: ```html <script> /** inlined runtime */ </script> <script src="/app/themes/sage/public/app.67d1d3.js" type="defer"></script> <link rel="stylesheet" href="/app/themes/sage/public/app.8083ce.css" /> ``` Obvious advantage: barring a more sophisticated way of parsing `entrypoints.json`, a project can do something like a php require of this file and be done with it.

tedw · May 31, 2022, 8:54pm

@ben That’s exactly what I was looking for, thanks!

For future reference, here’s the code:

bud.extensions.get('@roots/bud-entrypoints').setOption('emitHtml', true)