Typescript undefined error produced for defined enum

Question

In file defs.ts I define an enum and export it...

enum MyState {
    state1 = 'state1'
    state2 = 'state2'
... state5 = 'state5'
}

this gets exported to index.tsx of a Component and exported from there

export {
    MyState,
    ... 
}

It then gets imported into a file in another Component

import { MyState } from "../Component1"

const filterMap: { [key: string]: { title: string; filter: object } } = {
  s1: { title: 's1', filter: { state: MyState.state1 } },
  s2: { title: 's2', filter: { state: MyState.state2 } },
  s2: { title: 's3', filter: { state_ne: [MyState.state3 ] } },
}

However on being run, an error gets generated

Uncaught TypeError: Cannot read properties of undefined (reading 'MyState')

WTF is going on?

DocCaliban · Accepted Answer · 2022-04-11 23:06:46Z

1

This works for me

defs.ts

export enum MyState {
    state1 = 'state1',
    state2 = 'state2',
    state5 = 'state5',
}

Component2.tsx

import { MyState } from './defs'
const filterMap: { [key: string]: { title: string; filter: object } } = {
  s1: { title: 's1', filter: { state: MyState.state1 } },
  s2: { title: 's2', filter: { state: MyState.state2 } },
  s2: { title: 's3', filter: { state_ne: [MyState.state5 ] } },
}

If you need to export it from an intermediary you would do something like this.

Component1.tsx

export * from './defs'

I

answered Apr 11, 2022 at 23:06

DocCaliban

1,1649 silver badges14 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

vogomatix Over a year ago

Yep it appears adding an intermediary layer upsets things - thanks

Collectives™ on Stack Overflow

Typescript undefined error produced for defined enum

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related