Why Deno uses URL-based imports - See It in Action

Understanding URL-based Imports in Deno

📖 Scenario: You are learning how Deno manages code dependencies differently from traditional Node.js projects. Instead of using package managers and local node_modules folders, Deno uses URLs to import modules directly from the web or local files.

🎯 Goal: Build a simple Deno script that imports a module using a URL and uses it to perform a task. This will help you understand why Deno uses URL-based imports and how it works in practice.

📋 What You'll Learn

Create a Deno script file named main.ts.

Import a module from a URL using an import statement.

Use the imported module in your code to perform a simple function.

Run the script with Deno to see the result.

💡 Why This Matters

🌍 Real World

Many modern web and server projects use Deno for its secure and simple module system that relies on URLs instead of package managers.

💼 Career

Understanding URL-based imports in Deno is valuable for developers working on secure, scalable JavaScript and TypeScript applications, especially in cloud and edge environments.

1

Create a Deno script file with a URL import

Create a file named main.ts and write an import statement that imports the format function from https://deno.land/std@0.177.0/datetime/mod.ts.

Deno

// Your code here
// Import the format function from the URL

Hint

Use the import keyword followed by curly braces to import format from the exact URL.

2

Add a date variable to format

Below the import, create a constant variable named date and assign it the current date and time using new Date().

Deno

import { format } from "https://deno.land/std@0.177.0/datetime/mod.ts";

// Your code here
// Create a constant named date with the current date and time

Hint

Use const date = new Date(); to get the current date and time.

3

Use the imported format function to format the date

Use the format function to format the date variable into a string with the pattern yyyy-MM-dd HH:mm:ss. Assign the result to a constant named formattedDate.

Deno

import { format } from "https://deno.land/std@0.177.0/datetime/mod.ts";

const date = new Date();

// Your code here
// Format the date using format() and assign to formattedDate

Hint

Call format(date, "yyyy-MM-dd HH:mm:ss") and assign it to formattedDate.

4

Print the formatted date to the console

Add a line that prints the formattedDate to the console using console.log.

Deno

import { format } from "https://deno.land/std@0.177.0/datetime/mod.ts";

const date = new Date();

const formattedDate = format(date, "yyyy-MM-dd HH:mm:ss");

// Your code here
// Print formattedDate to the console

Hint

Use console.log(formattedDate); to display the formatted date.

Practice

1. Why does Deno use URL-based imports instead of traditional package managers?

easy

A. To allow direct loading of code from the web without extra tools

B. Because URLs are faster than local files

C. To force users to always be online

D. Because it does not support local files

Solution

1. Step 1: Understand Deno's import system

   Deno imports modules directly using URLs, unlike Node.js which uses package managers like npm.

2. Step 2: Reason why URLs are used

   This design removes the need for separate package managers or local installs, simplifying dependency management.

3. Final Answer:

   To allow direct loading of code from the web without extra tools -> Option A

4. Quick Check:

   Direct web imports = To allow direct loading of code from the web without extra tools [OK]

Hint: Remember: Deno loads code directly from URLs, no package manager needed [OK]

Common Mistakes:

• Thinking URLs are slower than local files
• Believing Deno requires always online connection
• Assuming Deno cannot use local files

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

easy

A. require('https://deno.land/std/http/server.ts');

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

C. import serve from 'http://localhost/server';

D. import * as serve from './server.ts';

Solution

1. Step 1: Identify correct import syntax in Deno

   Deno uses ES module syntax with import and URLs as module specifiers.

2. Step 2: Check each option

   import { serve } from 'https://deno.land/std/http/server.ts'; uses correct ES import with a full HTTPS URL. import serve from 'http://localhost/server'; uses HTTP but is less common and may be insecure. require('https://deno.land/std/http/server.ts'); uses Node.js style require, which Deno does not support. import * as serve from './server.ts'; imports local file, not URL.

3. Final Answer:

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

4. Quick Check:

   ES import + HTTPS URL = import { serve } from 'https://deno.land/std/http/server.ts'; [OK]

Hint: Look for ES import with full HTTPS URL syntax [OK]

Common Mistakes:

• Using Node.js require() instead of import
• Using local file path instead of URL
• Using HTTP instead of HTTPS

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

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

serve(() => new Response('Hello from Deno!'), { port: 8000 });

medium

A. Runs but does not respond to HTTP requests

B. Throws a syntax error because of missing semicolons

C. Starts an HTTP server on port 8000 responding with 'Hello from Deno!'

D. Fails to run because local server.ts file is missing

Solution

1. Step 1: Understand the imported module and function

   The serve function from Deno's standard library starts an HTTP server.

2. Step 2: Analyze the code behavior

   The code starts a server on port 8000 that responds with 'Hello from Deno!' to any request.

3. Final Answer:

   Starts an HTTP server on port 8000 responding with 'Hello from Deno!' -> Option C

4. Quick Check:

   serve() starts server with response = Starts an HTTP server on port 8000 responding with 'Hello from Deno!' [OK]

Hint: Recognize serve() starts HTTP server with given response [OK]

Common Mistakes:

• Thinking semicolons are mandatory in Deno
• Assuming local files are needed for URL imports
• Believing server won't respond without extra setup

4. You wrote this import in Deno:

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

But it throws an error. What is the likely cause?

medium

A. The URL is missing the file extension '.ts'

B. Deno does not support HTTPS URLs

C. You must use require() instead of import

D. The server module does not export 'serve'

Solution

1. Step 1: Check URL correctness for Deno imports

   Deno requires full file paths including extensions like '.ts' in URLs.

2. Step 2: Identify error cause

   The import URL lacks '.ts' extension, causing Deno to fail resolving the module.

3. Final Answer:

   The URL is missing the file extension '.ts' -> Option A

4. Quick Check:

   Missing file extension in URL = The URL is missing the file extension '.ts' [OK]

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

Common Mistakes:

• Thinking HTTPS URLs are unsupported
• Using require() instead of import
• Assuming module exports are missing

5. You want to share a Deno script with a friend without using npm or other package managers. How does Deno's URL-based import system help you achieve this?

hard

A. You have to send your friend all local files to install

B. You must bundle all dependencies into one file manually

C. You need to publish your code to npm first

D. You can host your modules on a web server and import them via URLs directly

Solution

1. Step 1: Understand Deno's URL import advantage

   Deno allows importing modules directly from URLs, so code can be shared via web hosting.

2. Step 2: Apply this to sharing scripts

   By hosting your modules online, your friend can import them directly without installing packages or bundling.

3. Final Answer:

   You can host your modules on a web server and import them via URLs directly -> Option D

4. Quick Check:

   URL imports enable direct sharing = You can host your modules on a web server and import them via URLs directly [OK]

Hint: Host modules online to share via URL imports easily [OK]

Common Mistakes:

• Thinking you must bundle dependencies manually
• Assuming npm is required for sharing
• Believing local files must be sent physically