Deprecate JSON as preload destination in favor of modulepreload #11995
Description
What is the issue with the HTML Standard?
In #11981 (review), @annevk raised a good point that JSON doesn't really make sense as a destination for preload if it also exists in modulepreload. script and style make sense in both, as there are use cases outside of modules, but as far as I understand, JSON is only natively supported as a JSON module import, so if it's being preloaded, it might as well go straight into the module map.
Chromium doesn't currently support <link type="preload" as="json"> (see https://wpt.fyi/results/preload/preload-type-match.html), but Firefox and Safari Preview do, so usage is probably low. I also don't believe there are any observable effects of preloading that could break a site by deprecating preload for JSON in favor of modulepreload - it doesn't look like <link> supports onload or onerror that could break by deprecating this.
Curious what your thoughts are @rniwa