Deno logoDenoby example



Dependency Management

It is unwieldy to have to import the same remote module over and over again. Deno provides some conventions to make managing dependencies easier.

The Deno ecosystem has a convention to re-export all remote dependencies from a deps.ts file at the root of the repo. This keeps remote dependencies organized, and in a single place.
export * as http from "";
export * as path from "";
Other files can then import dependencies from the deps.ts file.
import { path } from "./deps.ts";
Doing this makes package version upgrades really easy, as all external dependency specifiers live in the same file.

Additional resources: