2019-01-23
1668
#react#typescript
Dan Vanderkam
262
Jan 23, 2019 ⋅ 5 min read

How TypeScript breaks referential transparency

Dan Vanderkam Dan is a Principal Software Engineer at Sidewalk Labs and the author of Effective TypeScript: 62 Specific Ways to Improve Your TypeScript (O'Reilly 2019). He blogs regularly at effectivetypescript.com.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 ⋅ 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 ⋅ 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 ⋅ 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 ⋅ 12 min read
View all posts

One Reply to "How TypeScript breaks referential transparency"

  1. Nowadays in ts we have `as const` which will type out a tuple as the type you expect. (It also works for deeply nested objects)

Leave a Reply