TypeScript support out of the box in Deno - Step-by-Step Execution

Concept Flow - TypeScript support out of the box

Write TypeScript code

↓

Run with deno run

↓

Deno compiles TypeScript

↓

Execute compiled JavaScript

↓

Output result or error

Deno automatically compiles TypeScript code when you run it, then executes the compiled JavaScript without extra setup.

Execution Sample

Deno

const greet = (name: string): string => {
  return `Hello, ${name}!`;
};

console.log(greet("Deno"));

This code defines a TypeScript function and logs a greeting, showing Deno compiling and running TypeScript directly.

Execution Table

Step	Action	Evaluation	Result
1	Read TypeScript code	const greet = (name: string): string => {...}	Code loaded
2	Compile TypeScript to JavaScript	Type annotations removed, code converted	JavaScript code ready
3	Execute JavaScript code	Call greet("Deno")	Returns 'Hello, Deno!'
4	Console.log output	Print greeting	Output: Hello, Deno!

💡 Execution stops after printing the greeting to console.

Variable Tracker

Variable	Start	After greet call	Final
name	undefined	"Deno"	"Deno"
greet(name)	function	"Hello, Deno!"	"Hello, Deno!"

Key Moments - 2 Insights

Why don't I need to manually compile TypeScript before running with Deno?

Deno automatically compiles TypeScript behind the scenes when you run the file, as shown in execution_table step 2.

What happens to TypeScript type annotations during execution?

Type annotations are removed during compilation (step 2), so only plain JavaScript runs, ensuring no runtime overhead.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result after step 3?

A TypeScript code

B Compilation error

C "Hello, Deno!"

D Undefined

💡 Hint

Check the 'Result' column in execution_table row for step 3.

At which step does Deno convert TypeScript to JavaScript?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Action' column describing compilation.

If you remove the type annotations, how does the execution_table change?

A Step 2 is skipped

B No change, code runs the same

C Step 3 changes to a syntax error

D Step 4 outputs an error

💡 Hint

Type annotations are removed during compilation anyway, so runtime is unaffected.

Concept Snapshot

Deno runs TypeScript files directly.
It compiles TypeScript to JavaScript automatically.
No manual build step needed.
Type annotations are removed before execution.
Run with: deno run yourfile.ts
Output is JavaScript behavior.

Full Transcript

Deno supports TypeScript out of the box by compiling it automatically when you run a TypeScript file. You write TypeScript code with types, and Deno compiles it to JavaScript behind the scenes before running it. This means you do not need to run a separate compiler step. The type annotations are removed during compilation, so the runtime executes plain JavaScript. For example, a function with typed parameters runs normally and prints output. The execution steps include reading the code, compiling it, executing the JavaScript, and printing the result. This makes working with TypeScript easy and fast in Deno.

Practice

1. What is a key feature of Deno regarding TypeScript support?

easy

A. Deno does not support TypeScript at all.

B. Deno requires manual compilation of TypeScript before running.

C. Deno runs TypeScript files directly without extra setup.

D. Deno only supports JavaScript, not TypeScript.

Solution

1. Step 1: Understand Deno's TypeScript handling

   Deno is designed to run TypeScript files directly without needing a separate compilation step.

2. Step 2: Compare options with this feature

   Only Deno runs TypeScript files directly without extra setup. correctly states this direct support; others contradict this fact.

3. Final Answer:

   Deno runs TypeScript files directly without extra setup. -> Option C

4. Quick Check:

   Direct TypeScript execution = A [OK]

Hint: Remember: Deno runs TS files without compiling first [OK]

Common Mistakes:

• Thinking Deno needs manual TypeScript compilation
• Believing Deno only supports JavaScript
• Confusing Deno with Node.js setup

2. Which of the following is the correct way to run a TypeScript file named app.ts using Deno?

easy

A. deno compile app.ts

B. tsc app.ts && deno run app.js

C. node app.ts

D. deno run app.ts

Solution

1. Step 1: Identify Deno command to run TS files

   Deno uses deno run to execute TypeScript files directly.

2. Step 2: Evaluate other options

   deno compile app.ts compiles but does not run; tsc app.ts && deno run app.js compiles manually then runs JS, which is unnecessary; node app.ts uses Node.js which can't run TS directly.

3. Final Answer:

   deno run app.ts -> Option D

4. Quick Check:

   Run TS file with 'deno run' = C [OK]

Hint: Use 'deno run' to execute TypeScript files directly [OK]

Common Mistakes:

• Trying to compile TS manually before running
• Using Node.js command for TS files
• Confusing compile and run commands

3. Given this TypeScript code run with Deno:

function greet(name: string) {
  return `Hello, ${name}!`;
}
console.log(greet(42));

What will happen when you run deno run on this file?

medium

A. It throws a type error before running

B. It prints 'Hello, 42!'

C. It prints 'Hello, undefined!'

D. It runs but logs 'Hello, 42!' with a warning

Solution

1. Step 1: Analyze TypeScript type checking

   The function expects a string, but 42 is a number, causing a type error.

2. Step 2: Understand Deno's behavior

   Deno checks types before running and will throw an error, stopping execution.

3. Final Answer:

   It throws a type error before running -> Option A

4. Quick Check:

   Type mismatch causes error = A [OK]

Hint: Type errors stop Deno before running code [OK]

Common Mistakes:

• Assuming Deno runs code ignoring type errors
• Thinking it prints with warnings
• Confusing runtime errors with type errors

4. You wrote this TypeScript code:

const add = (a: number, b: number) => a + b;
console.log(add('5', 10));

When running with Deno, you get an error. What is the best fix?

medium

A. Remove type annotations from the function.

B. Change '5' to 5 (number) in the function call.

C. Run with Node.js instead of Deno.

D. Ignore the error and run anyway.

Solution

1. Step 1: Identify the type mismatch

   The function expects numbers, but '5' is a string, causing a type error.

2. Step 2: Fix the argument type

   Changing '5' (string) to 5 (number) matches the expected types and fixes the error.

3. Final Answer:

   Change '5' to 5 (number) in the function call. -> Option B

4. Quick Check:

   Correct argument types fix errors = B [OK]

Hint: Match argument types to function parameters [OK]

Common Mistakes:

• Removing types loses safety
• Trying to run with Node.js without compiling
• Ignoring errors instead of fixing types

5. You want to write a Deno script that reads a JSON file and ensures the data matches a TypeScript interface before processing. Which approach best uses Deno's TypeScript support out of the box?

hard

A. Define the interface, read the file, parse JSON, and use a type assertion to check the data.

B. Write JavaScript code and manually check types at runtime with if statements.

C. Compile the TypeScript to JavaScript first, then run with Deno.

D. Use a third-party tool to convert JSON to TypeScript types before running.

Solution

1. Step 1: Use TypeScript interface for type safety

   Defining an interface helps TypeScript check data structure during development.

2. Step 2: Read and parse JSON, then assert type

   Parsing JSON and using a type assertion leverages Deno's built-in TypeScript support to catch errors early.

3. Final Answer:

   Define the interface, read the file, parse JSON, and use a type assertion to check the data. -> Option A

4. Quick Check:

   Use interfaces and assertions for type safety = D [OK]

Hint: Use interfaces and type assertions with Deno's TS support [OK]

Common Mistakes:

• Ignoring TypeScript interfaces and relying on runtime checks
• Compiling manually before running with Deno
• Overcomplicating with external tools unnecessarily