<p dir="auto">We now can use kv-storage in chrome with:</p>
<div class="highlight highlight-source-js notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="import storageArea from 'std:kv-storage';"><pre class="notranslate"><span class="pl-k">import</span> <span class="pl-s1">storageArea</span> <span class="pl-k">from</span> <span class="pl-s">'std:kv-storage'</span><span class="pl-kos">;</span></pre></div>
<p dir="auto">How about support similar API for deno_std?</p>
<p dir="auto">It may looks like this, and imports the std module with the same version as the deno you installed.</p>
<div class="highlight highlight-source-js notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="import { serve } from 'deno_std:http/server';"><pre class="notranslate"><span class="pl-k">import</span> <span class="pl-kos">{</span> <span class="pl-s1">serve</span> <span class="pl-kos">}</span> <span class="pl-k">from</span> <span class="pl-s">'deno_std:http/server'</span><span class="pl-kos">;</span></pre></div>
<p dir="auto">And it's good to keep the same version between deno and deno_std modules.</p>
<p dir="auto">There is a <a href="https://github.com/tc39/proposal-javascript-standard-library/">Stage 1 TC39</a> proposal for "built in" browser modules to make a standard library for JavaScript.  It is proposing a <a href="https://github.com/tc39/proposal-javascript-standard-library/#protected-namespace">protected namespace</a> of <code class="notranslate">"std:"</code> for the module specifiers.  We should consider adopting this for potential standard built in modules.</p>