Yazan Alaboudi Which version of Typescript? https://www.typescriptlang.org/play/?ts=5.9.0-dev.20250404#code/PTAEDsFcFsFMCcCWBjUsrQFDpqAguItAIYA2oA3pqKADKID24ANNaACqIDmCrAvpkzImAZwAuoAFaRxeAHIwARggBcEJQlABeUAFYA3IJCg5DUGICeAB1hp48BvCGiJ0CwSJk1HkuR3TZBWhleEMjMHEkcC40DGwMfEJfACZKNhp6Jm1QAHJSRnAc1hoaTh54bJyxbgQczAFncHEpGTE8AGUxKK41SMRo7IAiADMGBkVieEGw43ZrWwQHeABCRua3HzJk7ySt7IC2zu79IA

Yazan Alaboudi Here's the issue that plagues only numeric enums, and not string enums: enum Animal { Lion, Tiger, } const justANumber: number = 5 ; // No type error const myAnimal: Animal = justANumber; Typescript made this historical error at some point and never tried to remedy it, let's say, by introducing a config such as strictNumericEnums: boolean .

People use string literal enums because numeric enums are completely backwards. Arbitrary numbers can be assigned to enums types, even when they are out of range. So numeric enum type is nothing more than just a number . Did something change since then?