<p dir="auto">I've been building an entire application to get my hands wet with deno. It's great so far. Thank you everyone for your hard work and contributions.</p>
<p dir="auto">A main development pain point I experience is importing new packages. I have to visit the package documentation, and get the url. Even for packages I have already used, I have to go to the documentation every time to copy the really long url.</p>
<p dir="auto">Now most of us deno users would be coming from npm, so it'd be more productive to be able to use common packages without having to visit documentations all the time to copy the url.</p>
<p dir="auto">With node, I could just <code class="notranslate">npm i express</code>, then <code class="notranslate">require('express')</code>, because <code class="notranslate">express</code> is easy to remember.</p>
<p dir="auto">My suggestion is to have similar functionality with deno. We could have an alias for urls. For example, <code class="notranslate">import * as log from 'log'</code> resolves to <code class="notranslate">import * as log from 'https://deno.land/std/log/mod.ts'</code>. Deno just resolves the alias behind the scenes.</p>
<p dir="auto">I hope the suggestion makes sense. Looking forward to what you think, or any drawbacks and feedback. Thanks !</p>
<p dir="auto">This has probably cross your mind while in the early stages of development in Deno, but what about an alias standard for packages?</p>
<p dir="auto">If I wanna import say React into most of my files I may not wanna write its url into each one(gotta admit it's kinda ugly), so why not reference it once into a file that act as a synonim of it so i can use it into my project?</p>
<p dir="auto">First thoughts were something like this (not that it is any prettier but will do)</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/42647963/68537684-332e2180-0336-11ea-80aa-d756dce013c2.png"><img src="https://user-images.githubusercontent.com/42647963/68537684-332e2180-0336-11ea-80aa-d756dce013c2.png" alt="image" style="max-width: 100%;"></a></p>
<p dir="auto">This isn't really a feature but more of a standard for Deno development to maybe be included into the documentation now that 1.0 is coming close.</p>