| > there is not really a difference between a url to a registry and a npm package name. There is. For starters, I can run my company's registry and make sure all npm packages are downloaded from there since resolution mechanism for npm/yarn is well known. How do I tell deno to download <random-url> from my own registry? Looking at how deno "solves" this I can't stop laughing [1] --- start quote --- In Deno there is no concept of a package manager as external modules are imported directly into local modules. This raises the question of how to manage remote dependencies without a package manager. In big projects with many dependencies it will become cumbersome and time consuming to update modules if they are all imported individually into individual modules. The standard practice for solving this problem in Deno is to create a deps.ts file. All required remote dependencies are referenced in this file and the required methods and classes are re-exported. The dependent local modules then reference the deps.ts rather than the remote dependencies... With all dependencies centralized in deps.ts, managing these becomes easier. --- end quote --- Are you for real? [1] https://deno.land/manual/examples/manage_dependencies |