Typescript Enums: The Good, The Bad, and The Ugly

Typescript Enums: The Good, The Bad, and The Ugly

Written by David Abram

Enums, short for "enumerations," are a type of data structure commonly found in programming languages. An enum defines a set of named values, typically representing a collection of related constants or options.

Instead of using arbitrary values or strings to represent these options, you can use an enum to enforce type safety and provide a clear and predefined list of choices.

Before JavaScript gets their own enums, we are stuck with TypeScript.

TypeScript enums seem to fit right in with types, interfaces and all-around typesafety of TypeScript, but there are curiously underutilized in most ts codebases.

enum TypeScript {


The Good

In TypeScript, similarly to any other language, enum variants can be assigned to a number or a string value. These values can't be reassigned later in the code.

enum Role {
  User = 10,
  Admin = 50

The cool part is that you can compare and manipulate enum variant values, so you can write something like:

const userRole = Role.User;

if(userRole >= Role.Admin) {
  console.log("User is admin");

This way you can always compare the enum variant values create conditional statements based on them. For example, you can write an if statement that checks whether the userRole is greater than or equal to Role.Admin.

If you create a conditional statement using enums which can never be satisfied, like in the code below, tsc will throw an compile time error.

const userRole = Role.User;

if(userRole !== Role.User || userRole !== Role.Admin) {
  // Error: This comparison appears to be unintentional 
  // because the types 'Role.User' and 'Role.Admin' have no overlap.

When creating discriminated unions, you can use an enum as their kinds. This way your conditional statements using discriminated unions don't need to have hardcoded values and can have all the upsides of enums.

enum ShapeKind {
  Circle = "CIRCLE",
  Square = "SQUARE",
  Triangle = "TRIANGLE"

// Shape type definition using discriminated unions
type Shape =
  | { kind: ShapeKind.Circle; radius: number }
  | { kind: ShapeKind.Square; x: number }
  | { kind: ShapeKind.Triangle; x: number; y: number };

// returns area of a shape
function area(s: Shape) {
  switch(s.kind) {
    case ShapeKind.Circle:
      return Math.PI * s.radius * s.radius;
    case ShapeKind.Square:
      return s.x * s.x;
    case ShapeKind.Triangle:
      return (s.x * s.y) / 2;
      throw new Error('Invalid shape');

To summarize everything, the good things about enums are:

šŸ‘‰ They can be assigned either numeric or string values, and these values cannot be reassigned later in the code.

šŸ‘‰ Enum variant values can be compared and manipulated, allowing for the creation of conditional statements based on them.

šŸ‘‰ If a conditional statement using enums is constructed in a way that can never be satisfied, the TypeScript compiler (tsc) will throw a compile-time error, helping to catch potential issues.

šŸ‘‰ Enums can be utilized as kinds in discriminated unions, enabling conditional statements without hardcoding values and leveraging the benefits of enums.

The Bad

Let's take the next example, and try to guess if '???' will be logged.

enum TypeScript {

const ts = TypeScript.Bad;

if(ts) {

Of course, the answer is yes. But why is that?

If you don't assign enum variant values, they will be assigned to 0, 1, 2, etc.

Well that means that first enum variant value will be falsy, and every other value will be truthy. šŸ˜ 

Remember how you can't reassign the enum variant values? Well, that's not entirely true. You can do it, but you shouldn't.

enum TypeScript {

(TypeScript as any).Bestest = 3; // This works!

Can we try to make enums readonly or freeze them?

enum TypeScript {

Object.freeze(TypeScript); // This works!

(TypeScript as any).Bestest = 3; // This throws an error

How can we use Object.freeze on an enum?

Well, TypeScript enums are actually just syntactic sugar for objects, under the hood they are just objects with keys and values.

Let's take a look at the compiled code:

"use strict";
var TypeScript;
(function (TypeScript) {
    TypeScript[TypeScript["Good"] = 0] = "Good";
    TypeScript[TypeScript["Bad"] = 1] = "Bad";
    TypeScript[TypeScript["Ugly"] = 2] = "Ugly";
})(TypeScript || (TypeScript = {}));
TypeScript.Bestest = 3;

So our TypeScript enum is just an object that looks like:

const TypeScript = {
  0: "Good",
  1: "Bad",
  2: "Ugly",
  Good: 0,
  Bad: 1,
  Ugly: 2,

TL;DR -> The bad things about enums are:

šŸ‘‰ TypeScript enums are essentially objects with keys and values.

šŸ‘‰ When enum variant values are not explicitly assigned, they are automatically assigned numeric values starting from 0. This means that the first enum value variant is falsy, while every other value is truthy.

šŸ‘‰ Although enum variant values are intended to be constants and should not be reassigned, it is technically possible to do so.

The Ugly

If you have read the previous section, you can compare and manipulate enum variant values, so you can write something like:

enum ShapeKind {
  Circle = "CIRCLE",
  Square = "SQUARE",
  Triangle = "TRIANGLE"

const circle = ShapeKind.Circle;

if(circle === "CIRCLE") {

In the if statement above, we are comparing an enum value with a string. This is a valid TypeScript code, but it's not a good practice.

Why you ask? Well, if you change the enum variant value, you will have to change the string value as well. This is a recipe for disaster.

So you can rewrite the whole thing like this:

type ShapeKind = "CIRCLE" | "SQUARE" | "TRIANGLE";

if(circle === "CIRCLE") {

This way you can avoid using enums, and you can still have similar level of type safety.

In both of these examples, if you don't enforce enums, you will have random hardcoded strings in your codebase.

If you haven't noticed, enums are objects, so you can iterate over an enum.

enum ResponseState {

for (const r in ResponseState) {

You would expect this code to log Loading, Failure, Success, but it will log Loading, Failure, Success, 0, 1, 2.

Take a look at the previous section, and you will see how an enum is compiled to an object.

We can stop devs accidentally iterating over enums by using const enum instead of enum.

const enum ResponseState {

const l = ResponseState.Loading;

The previous code will be compiled to:

"use strict";
const l = 0 /* ResponseState.Loading */;

This way we can get enums without the runtime overhead, but... there are a lot of pitfalls with const enum. You should checkout TypeScript Handbook for more info.

šŸ‘‰ Comparing enums with hardcoded values: While it is possible to compare enum values with hardcoded values, it is generally not recommended.

šŸ‘‰ Enums in TypeScript are represented as objects, which means they can be iterated over.

šŸ‘‰ By using const enum instead of enum, you can eliminate the runtime overhead associated with enums. However, there are potential pitfalls and limitations with const enum that should be considered.

Type Envy: Enums in other languages

Let's take a moment to admire and be envious of the implementation of enums in other languages.

In java you can add getters to enums, private fields, constructors and assign tuple values to them.

So you can write something like:

enum States {
    MASSACHUSETTS("Massachusetts",  "MA",   6981974),
    MICHIGAN     ("Michigan",       "MI",   10077331);

    private final String full;
    private final String abbr;
    private final Integer population;

    private States(String full, String abbr, Integer population) {
        this.full = full;
        this.abbr = abbr;
        this.population = population;

    public String getFullName() {
        return full;

    public String getAbbreviatedName() {
        return abbr;

    public Integer getPopulation(){
        return population;

So you can initialize a state variable, and get the full name, abbreviated name and population of the state.

States state = States.MASSACHUSETTS;
System.out.println(state.getFullName()); // Output: Massachusetts
System.out.println(state.getAbbreviatedName()); // Output: MA
System.out.println(state.getPopulation()); // Output: 6981974

Pretty nice, right? šŸ«¶

Or even better in a certain crab language, enums are algebraic data types.

Rather than having an enum inside a struct, you can put data directly into each enum variant.

Afterwards, you can do cool stuff like pattern matching on the enum variants and extract the data from them.

enum Message {
    Move { x: i32, y: i32 },
    ChangeColor(i32, i32, i32),

struct User {
    username: String,
    email: String,
    age: i32

fn main() {
    let message_move = Message::Move { x: 10, y: 20 };
    let message_write = Message::Write(String::from("Hello, world!"));
    let message_change_color = Message::ChangeColor(255, 255, 255);
    let message_update_user = Message::UpdateUser(User {
        username: String::from("davidabram"),
        email: String::from("hello@crocoder.dev"),
        age: 33

I feel envious of Rust enums, and I would love to have something similar in TypeScript.

Very nice! šŸ¦€šŸ¦€šŸ¦€šŸ¦€šŸ¦€


Enums are a useful data structure in programming languages. TypeScript enums are a fine tool for creating a set of related constants or options. Depending on the use case, ts enums go really quickly from useful to bad, to ugly.

Personally, I can't wait for JavaScript to get their own enums, so we can finally have a good implementation of enums in TypeScript.