Local dependencies

Make sure you are on the 4-local-depedencies branch to follow along with this section.

First let's look at how Deno handles local dependencies. We'll do that by creating a local dependency and importing it into our main "app.ts" file.

  • Add a file to the project called "utils.ts".
  • Add a const called "utils".
  • Add a function to that const that reverses a string.
  • Export the utils constant as the default export.
const utils = {
  reverse(text: string) {
    return text.split("").reverse().join();

export default utils;

In the "app.ts" file, require the utils module. Note that you will have to specify the file extension. Unlike Node, Deno does not allow you to import a module without an extension. This is the one way in which it differs from the ECMAScript spec.

import utils from "./utils.ts";

From the "app.ts" file, call the reverse method and log out the value.

import utils from "./utils.ts";

console.log(utils.reverse("Hello World"));

Execute the program and review the output...

Check file:///home/burkeholland/dev/deno-first-look-exercises/app.ts
dlroW olleH

Let's examine how Deno handled this dependency locally.

  • Open the generated output by navigating to the Deno cache folder...



// on my machine, it looks like this...



// on my machine, it looks like this...

You should see the following files present...

  • app.ts.buildinfo
  • app.ts.js
  • app.ts.js.map (This file may or may not be present. If it's not, it's because sourcemaps are included in the app.ts.js file.)
  • app.ts.meta
  • utils.ts.js
  • utils.ts.meta

If you open the app.ts.js file, you'll see that the utils file is being included and it's output has been transpiled here.

This should look familiar based on what we reviewed during the TypeScript section. Next we'll look at how this changes (or doesn't) when you install dependencies from other sources. Remote Dependencies.