<p dir="auto">after failing to install 1.3.1 it still seems to be going back to that failed version.<br>
Trying explicit --version fails also with:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="$ cargo install deno --version 1.3.2 
    Updating crates.io index
error: could not find `deno` in registry `https://github.com/rust-lang/crates.io-index` with version `=1.3.2`"><pre class="notranslate"><code class="notranslate">$ cargo install deno --version 1.3.2 
    Updating crates.io index
error: could not find `deno` in registry `https://github.com/rust-lang/crates.io-index` with version `=1.3.2`
</code></pre></div>
<p dir="auto">This would eliminate the need for modules like <a href="https://github.com/denosaurs/plug">plug</a> and <a href="https://github.com/manyuanrong/deno-plugin-prepare">deno-plugin-prepare</a> making plugins way more accessible. Allowing <code class="notranslate">Deno.openPlugin</code> to take a URL specifier would also make it possible for deno to directly cache the binary like a dependency (which <a href="https://github.com/denosaurs/plug">plug</a> already does but using a <a href="https://github.com/denosaurs/cache">separate dependency</a>) and reload the binary when the <code class="notranslate">--reload</code> flag is provided. The <code class="notranslate">Deno.openPlugin</code> should be able to take both remote and local urls to the binary and could possibly infer the url from os <del>and architecture</del> like <a href="https://github.com/denosaurs/plug">plug</a> does.</p>