The keyword and the hash are not two spellings of the same idea, and choosing by taste causes trouble later. The keyword is compile time only. It disappears entirely when compiled. At runtime the property is an ordinary…
I keep writing config objects and route maps and I have three ways to type them, all of which compile. Annotating the variable with the type. Casting the literal with . Or putting after it. They behave differently in…
The check is right there. Nothing between them touches . What confuses me more is that the same pattern inside sometimes compiles fine and sometimes does not, so I clearly do not understand the rule at all.
TypeScript 5.8. I have the standard recursive path type over a config object: Worked fine while the config was four levels deep. I added one more level and now gives me: The config has 9 top level keys and nothing…
returns . returns . returns an . Today that is three overloads and an implementation signature that is frankly a lie held together with . Someone on the team wants to replace it with a conditional return type driven by…
Six packages in a pnpm workspace, roughly 1,400 files, no project references yet everything resolves through path aliases into source. is already on. Full is 96 seconds and tsserver climbs to about 4 GB and restarts…
Internal API, about 40 endpoints, two of us. I want runtime validation at the boundary and types that cannot drift from it. There is an OpenAPI document generated from the handlers today but nobody fully trusts it.…
Six months into TypeScript, coming from JS. I parse a request body with zod and then write because the hover tooltip on the parse result is an unreadable wall of and I already have a interface defined for the rest of…