What is the main advantage of TypeScript compared to JavaScript?
TypeScript adds static types to JavaScript, helping catch errors early before running the code.
Click to reveal answer
beginner
How does TypeScript improve code readability?
By using types, TypeScript makes it clear what kind of data each variable or function expects, making code easier to understand.
Click to reveal answer
beginner
What happens if you try to assign a wrong type to a variable in TypeScript?
TypeScript will show an error during development, preventing potential bugs before running the program.
Click to reveal answer
beginner
Can TypeScript code run directly in browsers?
No, TypeScript code is compiled into JavaScript, which browsers can run.
Click to reveal answer
intermediate
Why might a team prefer TypeScript for large projects?
Because TypeScript helps manage complex code with types, making it easier to maintain and reduce bugs as the project grows.
Click to reveal answer
What feature does TypeScript add to JavaScript?
AStatic typing
BAutomatic UI rendering
CBuilt-in database support
DDirect browser execution
✗ Incorrect
TypeScript adds static typing to JavaScript, helping catch errors early.
Which of these is a benefit of using TypeScript?
ARuns faster than JavaScript in browsers
BDetects type errors before running code
CRequires no compilation
DRemoves the need for functions
✗ Incorrect
TypeScript detects type errors during development before running the code.
How does TypeScript help teams working on big projects?
ABy automatically writing code
BBy making code harder to read
CBy removing the need for testing
DBy improving code maintainability with types
✗ Incorrect
TypeScript improves maintainability by making types clear and catching errors early.
What must happen before TypeScript code runs in a browser?
AIt must be converted to HTML
BIt runs directly without changes
CIt must be compiled to JavaScript
DIt must be saved as a text file
✗ Incorrect
TypeScript code is compiled into JavaScript before running in browsers.
Which is NOT a reason to choose TypeScript over JavaScript?
ARun code faster in browsers
BAdd static types
CCatch errors early
DImprove code clarity
✗ Incorrect
TypeScript does not make code run faster in browsers; it focuses on development-time benefits.
Explain why TypeScript can help prevent bugs compared to JavaScript.
Think about how knowing data types before running code helps.
You got /4 concepts.
Describe how TypeScript supports large team projects better than plain JavaScript.
Consider how clear rules about data help many people work together.
You got /4 concepts.
Practice
(1/5)
1. Why do many developers choose TypeScript over plain JavaScript?
easy
A. Because TypeScript uses fewer lines of code than JavaScript
B. Because TypeScript runs faster in browsers than JavaScript
C. Because TypeScript does not require any compilation
D. Because TypeScript helps catch errors before running the code
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 D
Quick Check:
Type safety = Catch errors early [OK]
Hint: Remember: TypeScript finds bugs before running code [OK]
Common Mistakes:
Thinking TypeScript runs faster in browsers
Believing TypeScript needs no compilation
Assuming TypeScript always reduces code length
2. Which of the following is the correct way to declare a typed variable in TypeScript?
easy
A. let age = number 25;
B. let age: number = 25;
C. let age = 25: number;
D. let age number = 25;
Solution
Step 1: Recall TypeScript variable syntax
In TypeScript, the type comes after the variable name, separated by a colon, like let 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 B
Quick Check:
Variable: type = value [OK]
Hint: Type comes after variable name with colon [OK]
Common Mistakes:
Placing type before variable name
Using colon after value instead of after variable
Omitting colon between variable and type
3. What will be the output of this TypeScript code after compilation and running in JavaScript?
function greet(name: string) {
return `Hello, ${name.toUpperCase()}!`;
}
console.log(greet("world"));
medium
A. Hello, WORLD!
B. Error: name.toUpperCase is not a function
C. HELLO, WORLD!
D. Hello, 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"
Calling name.toUpperCase() on "world" returns "WORLD", so the output is "Hello, WORLD!".
Final Answer:
Hello, WORLD! -> Option A
Quick Check:
toUpperCase("world") = "WORLD" [OK]
Hint: Remember string methods like toUpperCase() work on strings [OK]
Common Mistakes:
Ignoring toUpperCase effect
Assuming output is all uppercase
Expecting runtime error due to types
4. Identify the error in this TypeScript code snippet:
function add(a: number, b: number) {
return a + b;
}
console.log(add(5, "10"));
medium
A. Type error: second argument should be a number, not a string
B. No error, outputs 15
C. Syntax error: missing return type
D. Runtime error: cannot add number and string
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 A
Quick Check:
Type mismatch argument = Error [OK]
Hint: Check argument types match parameter types [OK]
Common Mistakes:
Assuming implicit string to number conversion
Thinking missing return type causes error
Expecting runtime error instead of compile-time
5. You want to create a function in TypeScript that accepts either a string or a number and returns its string length or digit count. Which approach best uses TypeScript's features to handle this safely?
hard
A. Declare two separate functions, one for string and one for number
B. Declare the parameter as type any and convert it to string inside
C. Use a union type for the parameter and check its type inside the function
D. Use JavaScript without types to avoid complexity
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, use typeof to 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 C
Quick Check:
Union types + type guards = safe handling [OK]
Hint: Use union types and type checks for multiple input types [OK]
Common Mistakes:
Using any type loses type safety
Creating duplicate functions unnecessarily
Avoiding TypeScript features by using plain JavaScript
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.