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:

next js environmental variables

How to configure Next.js environmental variables

Learn how to manage environment variables in Next.js, which influence how an application behaves in different contexts and environments.

Joseph Mawa
Apr 25, 2025 ⋅ 9 min read
useActionState in React

useActionState in React: A practical guide with examples

Discover how React’s useActionState Hook makes it easier to handle user actions, especially form submissions and async state changes.

Rishi Purwar
Apr 25, 2025 ⋅ 5 min read
three js vs babylon js

Three.js vs. Babylon.js: Which is better for 3D web development?

Compare two libraries that support creating 3D experiences in the browser. Learn how to get started with each, their core features, and key differences.

Elijah Asaolu
Apr 24, 2025 ⋅ 7 min read
how to use the Next.js Image component to optimize images

How to use the Next.js Image component to optimize images

Explore automatic image optimization using Next Image, the built-in image optimization solution for Next.js.

Adebiyi Adedotun
Apr 23, 2025 ⋅ 7 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