Support json/style as modulepreload destinations

[noamr]

What is the issue with the HTML Standard?

json/css modules are available in import, however the modulepreload spec only allows script-like destinations (see https://html.spec.whatwg.org/multipage/links.html#link-type-modulepreload:link-type-modulepreload-3).

Allowing json/style here would allow preloading them for the purpose of imports.

[annevk]

Presumably they're already supported if they're deeper in the module graph. Just not as a top-level entry. I guess it makes sense to reuse the as attribute here?

cc @domenic @whatwg/modules

[noamr]

Presumably they're already supported if they're deeper in the module graph.

Right, in cases where modulepreload starts fetching the graph.

Just not as a top-level entry. I guess it makes sense to reuse the as attribute here?

Yes exactly, extend as to be script-like + json/style

cc @domenic @whatwg/modules

[noamr]

@nicolo-ribaudo WDYT?

[nicolo-ribaudo]

This is a good change -- it should be possible to use modulepreload to load all the components of an ESM graph.

Currently modulepreload is a subset of preload, however there is no use case for preload as=json so it makes sense to only support JSON in modulepreload.

[noamr]

This is a good change -- it should be possible to use modulepreload to load all the components of an ESM graph.

Currently modulepreload is a subset of preload, however there is no use case for preload as=json so it makes sense to only support JSON in modulepreload.

It's sort-of a subset, it also populates the module map and uses crossorigin by default.

[nicolo-ribaudo]

Yeah sorry, I meant "the possible resource types you can load with modulepreload are a subset of those you can load with preload".