TypeScript Strings
Understand TypeScript Strings
Strings are sequences of UTF-16 code units in JavaScript. TypeScript uses the string type to check string values; runtime string operations still follow JavaScript semantics.
What you will learn: the purpose of typescript strings, the rules TypeScript checks, and what its JavaScript behavior looks like in a runnable example.
What you’ll learn
- Explain how typescript strings works and where its type rules apply.
- Predict the exact output of the typescript strings example.
- Diagnose a common issue: Do not assume toUpperCase changes the original variable.
Build the mental model
Indexing and length use UTF-16 code units rather than user-perceived characters. Strings are immutable: methods return new strings instead of changing the original value. Template literals offer convenient interpolation.
Key distinction: TypeScript checks the declared types during development; emitted JavaScript carries out the value-level operation at runtime. A type declaration alone never validates untrusted runtime input.
See the relationship
Read this illustration from the first labeled part to the last. Compare it with the example and identify which parts are type checks and which parts run in JavaScript.
Run the complete TypeScript example
This self-contained example uses fixed values, so it runs without reading input or depending on an external service. Paste it into the TypeScript Playground or save it as main.ts.
TypeScript program
const language: string = "TypeScript";
console.log(language.length);
console.log(language[0]);
console.log(language.toUpperCase());
console.log(language);Verified output
10
T
TYPESCRIPT
TypeScriptRun locally: npx tsc --strict --target es2022 --module commonjs main.ts, then node main.js. For projects with a tsconfig.json, build using that configuration instead.
Trace every important step
length is 10 and index 0 is T. toUpperCase returns a new uppercase string. The original language stays TypeScript.
Check each step: identify the input values, follow the JavaScript operation in execution order, and match the final expression with the exact output shown. An annotation can reject invalid source before execution, but does not change the value printed.
Avoid these common mistakes
Do not assume toUpperCase changes the original variable. Avoid assuming string length always matches visible character count for emoji or combining sequences.
How to debug: reproduce the issue in a minimal example. For compiler errors, inspect the inferred and declared types; for a runtime surprise, log the actual values and follow their references or branches.
Practice and experiment
Store a full name and print its trimmed length, uppercase form, and first UTF-16 code unit.
Practice routine: predict the result on paper, edit one part of the code, compile under --strict, run the JavaScript, and explain whether TypeScript caught an error or JavaScript simply behaved differently.
Check your understanding
Review the key idea
TypeScript Strings: Strings are sequences of UTF-16 code units in JavaScript.
length is 10 and index 0 is T. toUpperCase returns a new uppercase string. The original language stays TypeScript.
Before continuing, explain one valid use case, one common pitfall, and the separation between compile-time checking and runtime behavior for this feature.
Reaching the recap and completing the quizzes are separate milestones.