String, Number and Boolean

String, Number and Boolean Overview

String, Number and Boolean is a core part of the TypeScript type system. Understanding it helps you model data accurately, catch mistakes early, and communicate intent to teammates through types.

We focus on practical patterns you will use in real codebases—not abstract theory. Examples mirror common frontend, backend, and library scenarios.

String, Number and Boolean Example

let title: string = "Report";
let pages: number = 12;
let draft: boolean = false;
const summary = `${title}: ${pages} pages`;

Primitives mirror JavaScript values with explicit compile-time contracts.

When to Use String, Number and Boolean

• Modeling data that requires string, number and boolean
• Reviewing or refactoring typed application code
• Building reusable libraries with clear contracts
• Onboarding developers to a TypeScript codebase
• Preparing for interviews on TypeScript fundamentals
• Pairing types with tests for critical business logic

Best Practices

• Use string, number and boolean to document intent at API boundaries
• Prefer inference for local variables when types are obvious
• Enable strict compiler options to maximize checking
• Name types clearly with domain language, not abbreviations
• Combine with narrowing when working with union types
• Review compiler errors instead of silencing with any
• Keep examples small and composable in production code

Common Mistakes to Avoid

• Over-annotating when inference already suffices
• Using type assertions instead of proper narrowing
• Applying patterns without understanding runtime behavior
• Ignoring null and undefined in strict mode
• Duplicating types instead of reusing aliases or interfaces
• Expecting types to validate external JSON automatically
• Mixing incompatible module settings with bundler output

Key Takeaways

• String, Number and Boolean strengthens contracts in TypeScript code
• Types are erased at compile time—validate external data separately
• Combine with interfaces, unions, and generics as needed
• Strict mode surfaces more issues during development
• Good naming makes complex types self-documenting
• Next: explore Arrays and Tuples to continue the course