Asset loading strategy problems about webpack HOT 2 CLOSED

Other than the granular as-it-streams loading, this might be solvable with a @marko/webpack taglib:

<marko-webpack-scripts />
<marko-webpack-styles />

(Names welcome for bikeshedding)

By placing them in the root templates, the developer can control where the injection points are, without overly complicating the inject-into-stream logic. Everything under point №1 is no longer a problem.

Additionally, the injected elements can be configured with attributes:

<marko-webpack-scripts 
  type="module"
  preload=(url => !url.includes('lazy'))
/>

This doesn’t solve everything in points №2 and 3, but it would solve many of them.

What do you think?

from webpack.

Problems 1 and 2 have been fixed. 3 adds enough scope it should probably be its own issue.

from webpack.