TypeScript's number type is a lie
TypeScript's number type lacks the ability to enforce type safety for different numerical units, leading to potential bugs in code. Developers often encounter issues when passing numbers with different meanings to functions expecting specific units. To mitigate this, some teams implement custom types and ESLint rules to ensure proper handling of numerical values with associated units.
- ▪TypeScript allows any number to be passed to functions without recognizing the unit of measurement.
- ▪This can lead to significant bugs, such as miscalculating time intervals or financial transactions.
- ▪Developers can create opaque type tags to differentiate between units but face challenges when performing arithmetic operations.
2 outlets in our directory ran this story. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ TypeScript’s number type is a lie — r/typescript
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Medium |
| Canonical URL | https://bluepnume.medium.com/typescripts-number-type-is-a-lie-6b3b10dd8f54 |
| Publication time | Wed, 27 May 2026 01:54:57 +0000 |
| Retrieval time | 2026-05-27T02:07:56.149Z |
| Last seen | 2026-05-27T02:07:56.149Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | iairbzrgqr-I · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
TypeScript’s number type is a lieDaniel Brain8 min read·Just now--ListenSharePress enter or click to view image in full size5000 is 5000 is 5000.It might be milliseconds. It might be seconds. It might be the year, the price in cents, the height in pixels, or the number of bytes in your payload. TypeScript has no idea. It will happily let you pass any of them to any function that takes a number. That is not type safety. That is a vibe.This is the bug you wrote last week:setTimeout(retry, 5); // 5 milliseconds, not 5 seconds. Whoops.This is the bug your coworker wrote:const expiresAt = Date.now() + ttl; // ttl is in seconds.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Medium.
Discussion
0 commentsMore from Medium
