Ignore `<script>` elements for bundle when they have [type] that is not empty or default or `module`

[zachleat]

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/script/type

https://github.com/11ty/eleventy-base-blog/blob/85d8740d20207ab531bfcc33bc7150969b0d57d2/eleventy.config.js#L48

[zachleat]

cc @vrugtehagel

[zachleat]

I wonder also if it’s worth segmenting module and not module in the eleventy-base-blog example

[vrugtehagel]

I guess this actually gets pretty complicated if you want to get it "right", but what "right" is also depends on a case-by-case basis. The docs say you can use an arbitrary selector for bundleHtmlContentFromSelector, but I couldn't get something like script:not([type]) to work properly; if more complex selectors like that work, then this would give users the maximum flexibility.

As an example, a <script defer> and <script> probably shouldn't be bundled together, since they are intended to run at different times. With complex selectors we can fix this using a script[defer] bucket (which already works) and a script:not([defer]) one (which currently doesn't).

That also solves the non-JS-type scripts, through script:not([type]), script[type="text/javascript"] (and potentially script[type="module"], depending on the needs). Having long selectors like that is not particularly pretty, but at least descriptive, and is transparent about its behavior.

[zachleat]

I would note that the pluck feature supports an eleventy:ignore attribute to skip and the prune empty bundle output feature supports an eleventy:keep attribute as a currently working workaround