TypeScript helps catch mistakes early by checking your code before running it. It adds clear rules about the types of data you use, making your code easier to understand and fix.
Why TypeScript over JavaScript
TypeScript code looks like JavaScript but adds types like: let age: number = 25; let name: string = "Alice"; function greet(person: string): string { return `Hello, ${person}!`; }
TypeScript files usually end with .ts instead of .js.
TypeScript needs to be converted (compiled) to JavaScript before running in browsers.
let count: number = 10; count = 20; // OK // count = "twenty"; // Error: Type 'string' is not assignable to type 'number'.
function add(a: number, b: number): number { return a + b; } let result = add(5, 3); // result is 8
interface Person {
name: string;
age: number;
}
let user: Person = { name: "Bob", age: 30 };This simple program shows how TypeScript uses types to make sure the function gets a string and returns a string.
function greet(name: string): string { return `Hello, ${name}!`; } console.log(greet("Alice"));
TypeScript helps find errors before running your code, saving time.
You can gradually add TypeScript to existing JavaScript projects.
Using TypeScript can improve your coding skills by making you think about data types.
TypeScript adds types to JavaScript to catch errors early.
It makes code easier to read, maintain, and work on with others.
TypeScript code needs to be converted to JavaScript to run in browsers.
Practice
Solution
Step 1: Understand TypeScript's main benefit
TypeScript adds types to JavaScript, which helps find mistakes early, before running the code.Step 2: Compare options with this benefit
Only Because TypeScript helps catch errors before running the code mentions catching errors early, which is the key reason developers prefer TypeScript.Final Answer:
Because TypeScript helps catch errors before running the code -> Option DQuick Check:
Type safety = Catch errors early [OK]
- Thinking TypeScript runs faster in browsers
- Believing TypeScript needs no compilation
- Assuming TypeScript always reduces code length
Solution
Step 1: Recall TypeScript variable syntax
In TypeScript, the type comes after the variable name, separated by a colon, likelet varName: type.Step 2: Check each option's syntax
Only let age: number = 25; uses the correct syntax:let age: number = 25;. Others have misplaced or missing colons.Final Answer:
let age: number = 25; -> Option BQuick Check:
Variable: type = value [OK]
- Placing type before variable name
- Using colon after value instead of after variable
- Omitting colon between variable and type
function greet(name: string) {
return `Hello, ${name.toUpperCase()}!`;
}
console.log(greet("world"));Solution
Step 1: Understand the function behavior
The function takes a string and returns "Hello, " plus the uppercase version of the name plus "!".Step 2: Apply the function to input "world"
Callingname.toUpperCase()on "world" returns "WORLD", so the output is "Hello, WORLD!".Final Answer:
Hello, WORLD! -> Option AQuick Check:
toUpperCase("world") = "WORLD" [OK]
- Ignoring toUpperCase effect
- Assuming output is all uppercase
- Expecting runtime error due to types
function add(a: number, b: number) {
return a + b;
}
console.log(add(5, "10"));Solution
Step 1: Check function parameter types
The function expects both parameters to be numbers.Step 2: Analyze the call with arguments (5, "10")
The second argument is a string, which conflicts with the expected number type, causing a TypeScript type error before running.Final Answer:
Type error: second argument should be a number, not a string -> Option AQuick Check:
Type mismatch argument = Error [OK]
- Assuming implicit string to number conversion
- Thinking missing return type causes error
- Expecting runtime error instead of compile-time
Solution
Step 1: Understand TypeScript union types
Union types allow a variable to be one of several types, e.g.,string | number.Step 2: Use type checking inside function
Inside the function, usetypeofto check if the input is string or number, then handle accordingly. This keeps type safety and clarity.Final Answer:
Use a union type for the parameter and check its type inside the function -> Option CQuick Check:
Union types + type guards = safe handling [OK]
- Using any type loses type safety
- Creating duplicate functions unnecessarily
- Avoiding TypeScript features by using plain JavaScript
Ready to prove it?
Pass the test and this pattern moves unknown
