🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸<p>&gt; <a href="https://mastodon.social/tags/Deno" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Deno</span></a> has taken a U-turn on <a href="https://mastodon.social/tags/HTTPimports" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTPimports</span></a> and <a href="https://mastodon.social/tags/JSR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JSR</span></a> does NOT allow them. JSR allows node:, npm:, and jsr: imports, but not http:.</p><p>&gt;This is a big deal because every single pre-JSR Deno <a href="https://mastodon.social/tags/package" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>package</span></a> with dependencies used HTTP imports. That was the Deno way. Those <a href="https://mastodon.social/tags/packages" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>packages</span></a> are now blocked from publishing on JSR until upstream packages do — if they do. Few are. Curiously, for an immutable registry, the package count is dropping.</p><p><a href="https://dbushell.com/2024/08/09/jsr-and-deno-final-review/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dbushell.com/2024/08/09/jsr-an</span><span class="invisible">d-deno-final-review/</span></a></p><p><a href="https://mastodon.social/tags/javaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>javaScript</span></a> <a href="https://mastodon.social/tags/webDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webDev</span></a> <a href="https://mastodon.social/tags/packagemanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>packagemanagement</span></a> <a href="https://mastodon.social/tags/js" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>js</span></a></p>