TypeScript 5.5 shipped with a mix of headline features and subtle improvements that compound significantly in large codebases. After running it in production for months, here are the features that actually moved the needle for our team.
The Big One: Inferred Type Predicates #
This sounds small but it's a massive DX improvement. TypeScript can now automatically infer type predicates from function implementations.
Before 5.5: The Verbose Manual Fix
// Before: TypeScript couldn't narrow the type
function isString(value: unknown): boolean {
return typeof value === 'string';
}
const values: (string | number)[] = ['hello', 42, 'world', 100];
// You'd have to do this:
const strings = values.filter((v) => {
if (isString(v)) {
return v; // TypeScript still thought v could be number!
}
return false;
});
// Or this (more explicit but verbose):
const strings = values.filter((v): v is string => isString(v));
After 5.5: Automatic Inference
// Now TypeScript infers the type predicate automatically
function isString(value: unknown): boolean {
return typeof value === 'string';
}
const values: (string | number)[] = ['hello', 42, 'world', 100];
// TypeScript now correctly narrows inside the filter callback
const strings = values.filter((v) => isString(v));
// strings is correctly typed as string[]
// Works with more complex predicates
function isNonNullable<T>(value: T): value is NonNullable<T> {
return value !== null && value !== undefined;
}
const mixed: (string | null | undefined)[] = ['a', null, 'b', undefined, 'c'];
const defined = mixed.filter(isNonNullable);
// defined is string[]
Where This Compounds: Data Validation Chains
// Before 5.5 required explicit type predicates everywhere
interface User {
id: string;
email: string;
role: 'admin' | 'user' | 'guest';
}
function isAdmin(user: User): boolean {
return user.role === 'admin';
}
function isActive(user: User): boolean {
return user.email.includes('@'); // simplified
}
const users: User[] = /* from API */;
// Old way: explicit type predicates
const admins = users.filter((u): u is User => isAdmin(u) && isActive(u));
// 5.5 way: inferred predicates chain naturally
const admins = users.filter((u) => isAdmin(u) && isActive(u));
Regular Expression Syntax Checking #
TypeScript 5.5 adds type checking for regular expressions. This catches real bugs.
Caught at Compile Time
// This would have been a runtime error before
const emailRegex = new RegExp('[a-z+', 'i'); // Syntax error in regex!
// TypeScript 5.5: Error detected at compile time
// Error: Invalid regular expression: Range out of order in character class
// Another example
const dateRegex = new RegExp('(\\d{4})-(\\d{2})-(\\d{2}', 'g'); // Missing closing paren
// Error: Invalid regular expression: Unterminated group
The Subtle Case It Catches
// Oops: accidentally escaped the wrong character
const phoneRegex = new RegExp('\\d{3}[-*]\\d{3}[-*]\\d{4}');
// Valid! But what if you meant:
const zipRegex = new RegExp('\d{5}'); // Missing backslash!
// TypeScript 5.5 catches this: '\d' should be '\\d' in string
// Error: Invalid escape sequence in string literal
Object Types from Array.filter() #
When you filter an array with a type predicate that narrows to a specific interface, TypeScript now properly infers the output type.
interface ApiResponse {
status: 'success' | 'error';
data?: object;
error?: string;
}
const responses: ApiResponse[] = await fetchAll();
// Before 5.5: You had to manually type the filter result
const successful: ApiResponse[] = responses.filter((r) => r.status === 'success');
// This worked but was verbose for more complex scenarios
// 5.5 handles discriminated unions better
const successes = responses.filter((r) => r.status === 'success');
// successes is (ApiResponse & { status: 'success' })[] but crucially
// r.data is now properly typed as `object` (not `object | undefined`)
The import Attributes Fix #
// Before 5.5: Weird edge cases with import assertions
import data from './data.json' assert { type: 'json' };
// 5.5: import attributes syntax (the new standard)
import data from './data.json' with { type: 'json' };
// This matters because `assert` is being deprecated in favor of `with`
// 5.5 ensures you're writing future-proof code
Performance: Faster Builds #
TypeScript 5.5 brought meaningful build speed improvements. In our codebase (~800k lines, 300 packages):
TypeScript 5.4: 45.2s full build
TypeScript 5.5: 38.7s full build
Improvement: ~14%
With --incremental:
TypeScript 5.4: 12.1s incremental
TypeScript 5.5: 9.8s incremental
Improvement: ~19%
The speedup comes from:
- More efficient type narrowing
- Smarter stale file detection
- Better caching of resolved imports
The new satisfies #
Behavior
// 5.5 refines what `satisfies` means for union types
type Color = 'red' | 'green' | 'blue';
type Theme = Record<string, Color | string>;
const theme = {
primary: 'red',
secondary: 'blue',
custom: '#3498db', // This is valid (string, not Color)
} satisfies Theme;
// TypeScript now correctly narrows each property
const primary: Color = theme.primary; // 'red' (not Color | string)
const custom: string = theme.custom; // '#3498db' (not Color | string)
// Before 5.5, you sometimes had to cast even with satisfies
What Didn't Change (And That's Okay) #
You Still Need Explicit Type Annotations for API Boundaries
// This still requires explicit types - TypeScript can't infer from runtime
async function fetchUser(id: string): Promise<User> {
// You still need to tell TypeScript what User is
const response = await fetch(`/api/users/${id}`);
return response.json(); // still any, needs type assertion or schema validation
}
// Best practice: use a schema validator (zod, typebox)
import { z } from 'zod';
const UserSchema = z.object({
id: z.string(),
email: z.string().email(),
role: z.enum(['admin', 'user', 'guest']),
});
const response = await fetch(`/api/users/${id}`);
const user = UserSchema.parse(await response.json()); // typed correctly
Complex Generics Still Need Help
// TypeScript still struggles with complex inference in some cases
function createReducer<S, A extends Action>(
initialState: S,
handlers: Record<string, (state: S, action: A) => S>
): Reducer<S, A> {
return (state = initialState, action) => {
const handler = handlers[action.type];
return handler ? handler(state, action) : state;
};
}
// The inference still requires explicit types in some scenarios
// This is fundamental to how TypeScript's type system works
Migration Guide: What to Change #
Step 1: Update TypeScript
npm install typescript@5.5 --save-dev
pnpm add -D typescript@5.5
Step 2: Find Type Predicate Boilerplate to Remove
Search your codebase for value is
patterns in filter callbacks:
// This pattern is now unnecessary in most cases:
array.filter((item): item is Type => predicate(item))
// Can become:
array.filter(predicate)
Step 3: Update import assertions to import attributes
// Replace:
import foo from './foo.json' assert { type: 'json' };
// With:
import foo from './foo.json' with { type: 'json' };
Step 4: Add RegExp Validation (Optional but Recommended)
// Add a lint rule to catch regex errors early
// ESLint rule: no-invalid-regexp
// Or add a custom rule in your CI:
const regex = new RegExp(pattern);
console.log('Regex valid:', regex.source);
The Bottom Line #
TypeScript 5.5 isn't a revolutionary release, but it's a solid incremental improvement. The inferred type predicates alone save hours of boilerplate in large codebases. The performance improvements compound on every build.
The real value: TypeScript is getting better at reducing the gap between what you write and what TypeScript understands, without requiring increasingly complex type gymnastics.
Running TypeScript 5.5? What's your experience been? Any surprises — good or bad?
Upgrade with confidence: npm install -D typescript@5.5 && npx tsc --version
source & further reading
dev.to — original article
Building Local AI Agents in Java with Tools4AI and Ollama: An Insurance Claims Use Case
Run and Compare AI Evaluations with a CLI for Developers and Coding Agents
We Open-Sourced Both Halves of Our Security Stack — Detection and Deliberation