Simple solution to the dependency management (spitballing): a directory of files where the filename is the module name. Each file is simply: <url><newline><s

Simple solution to the dependency management (spitballing): a directory of files where the filename is the module name. Each file is simply: <url><newline><size in bytes><newline><hash> And then in an application: import { serve } from deno.http.server; If you want nested levels so deno.X.X wouldn't be a ton of files you could possibly just do nested directories so deno/http/server would equate to deno.http.server. Most people would want the option to do dependency management on a per-project basis as well. Simply allow a command-line parameter to provide one or more other directories to source from first (besides presumably the global one for your installation). If we wanted the file to be generated automatically, maybe something like this: import { serve } from deno.http.server at "https://deno.land/std@0.50.0/http/server.ts";