Importing from URLs in Deno

Introduction

Importing from URLs lets you use code directly from the internet without downloading it first. This makes sharing and using code easy and fast.

You want to use a library or tool that is hosted online without installing it locally.

You are sharing code with others and want them to run it without extra setup.

You want to quickly test or use small utilities from the web.

You need to keep your code updated automatically from a remote source.

You want to avoid managing local dependencies manually.

Syntax

Deno

import { something } from "https://example.com/path/to/module.ts";

The URL must point to a valid JavaScript or TypeScript module.

Deno caches the imported modules locally after the first download.

Examples

This imports the serve function from Deno's standard library over the internet.

Deno

import { serve } from "https://deno.land/std@0.203.0/http/server.ts";

This imports everything from the logging module and names it log.

Deno

import * as log from "https://deno.land/std@0.203.0/log/mod.ts";

This imports the default export from a module hosted at a custom URL.

Deno

import defaultExport from "https://example.com/my-module.ts";

Sample Program

This program imports the serve function from Deno's standard library using a URL. It starts a simple web server on port 8000 that responds with a friendly message.

Deno

import { serve } from "https://deno.land/std@0.203.0/http/server.ts";

const server = serve({ port: 8000 });
console.log("Server running on http://localhost:8000/");

for await (const req of server) {
  req.respond({ body: "Hello from Deno!" });
}

Important Notes

Deno caches modules after the first import, so subsequent runs are faster and offline.

If the remote module changes, you can update your cache by running deno cache --reload.

Always use exact URLs with version numbers to avoid unexpected breaking changes.

Summary

Importing from URLs lets you use code directly from the web without local installs.

Deno caches these modules for speed and offline use.

Use versioned URLs to keep your code stable and predictable.

Practice

1. What is the main benefit of importing modules from URLs in Deno?

easy

A. You can use code directly from the web without installing it locally.

B. It makes your code run faster than local imports.

C. It automatically updates your code to the latest version.

D. It disables caching to always fetch fresh code.

Solution

1. Step 1: Understand URL imports in Deno

   Deno allows importing modules directly from web URLs, so you don't need to install packages locally.

2. Step 2: Identify the main benefit

   This feature simplifies using external code by fetching it on demand without manual installs.

3. Final Answer:

   You can use code directly from the web without installing it locally. -> Option A

4. Quick Check:

   Importing from URLs = No local install needed [OK]

Hint: Remember: URL imports mean no local installs needed [OK]

Common Mistakes:

• Thinking URL imports always update to latest code
• Believing URL imports disable caching
• Assuming URL imports make code run faster

2. Which of the following is the correct syntax to import a module from a URL in Deno?

easy

A. import { serve } from "https://deno.land/std/http/server.ts";

B. require("https://deno.land/std/http/server.ts");

C. import serve from "./server.ts";

D. load { serve } from "https://deno.land/std/http/server.ts";

Solution

1. Step 1: Recall Deno import syntax

   Deno uses ES module syntax with import { ... } from "url"; to import from URLs.

2. Step 2: Check each option

   import { serve } from "https://deno.land/std/http/server.ts"; uses correct ES module import syntax with a URL. require("https://deno.land/std/http/server.ts"); uses Node.js style require, which Deno does not use. import serve from "./server.ts"; imports locally, not from URL. load { serve } from "https://deno.land/std/http/server.ts"; uses invalid keyword load.

3. Final Answer:

   import { serve } from "https://deno.land/std/http/server.ts"; -> Option A

4. Quick Check:

   Correct import syntax = import { serve } from "https://deno.land/std/http/server.ts"; [OK]

Hint: Deno uses ES import syntax, not require or load [OK]

Common Mistakes:

• Using require() instead of import
• Trying to import local files with URL syntax
• Using invalid keywords like load

3. What will happen when you run this Deno code snippet?

import { serve } from "https://deno.land/std/http/server.ts";

console.log(typeof serve);

medium

A. "object"

B. "undefined"

C. Runtime error: Module not found

D. "function"

Solution

1. Step 1: Understand what is imported

   The serve function is exported from the URL module as a function.

2. Step 2: Check the typeof operator on serve

   Since serve is a function, typeof serve returns the string "function".

3. Final Answer:

   "function" -> Option D

4. Quick Check:

   typeof serve = "function" [OK]

Hint: Imported functions have typeof 'function' in JS/TS [OK]

Common Mistakes:

• Expecting 'undefined' if module loads correctly
• Thinking import causes runtime error
• Confusing function with object type

4. Identify the error in this Deno import statement:

import { serve } from "https://deno.land/std/http/server";

medium

A. URL must start with http:// not https://.

B. Using curly braces {} around serve is incorrect.

C. Missing file extension ".ts" in the URL.

D. Cannot import from URLs in Deno.

Solution

1. Step 1: Check URL correctness

   Deno requires full file paths including extensions for URL imports, so missing ".ts" causes error.

2. Step 2: Validate other parts

   Curly braces are correct for named imports. HTTPS is supported. Deno supports URL imports.

3. Final Answer:

   Missing file extension ".ts" in the URL. -> Option C

4. Quick Check:

   File extension required in URL imports [OK]

Hint: Always include file extensions in Deno URL imports [OK]

Common Mistakes:

• Omitting file extensions in import URLs
• Thinking HTTPS is unsupported
• Misunderstanding import syntax with braces

5. You want to ensure your Deno project always uses the same version of a library imported from a URL. Which practice helps achieve this?

hard

A. Disable Deno's cache to force fresh downloads every run.

B. Use a versioned URL like "https://deno.land/std@0.203.0/http/server.ts".

C. Manually download and import local copies only.

D. Import from the base URL without version to get latest updates.

Solution

1. Step 1: Understand versioning in URL imports

   Using versioned URLs locks the imported code to a specific release, ensuring stability.

2. Step 2: Evaluate options

   Use a versioned URL like "https://deno.land/std@0.203.0/http/server.ts". uses a versioned URL, which is best practice. Import from the base URL without version to get latest updates. fetches latest, risking breaking changes. Manually download and import local copies only. is manual and not URL import. Disable Deno's cache to force fresh downloads every run. disables caching, causing inefficiency.

3. Final Answer:

   Use a versioned URL like "https://deno.land/std@0.203.0/http/server.ts". -> Option B

4. Quick Check:

   Versioned URLs = stable imports [OK]

Hint: Lock versions in URL to keep imports stable [OK]

Common Mistakes:

• Using unversioned URLs expecting stability
• Disabling cache wastes time and bandwidth
• Confusing manual local imports with URL imports