Closes freeCodeCamp#605 `Explorer` could not see TypeScript enums at all, so curriculum tests had to fall back on regular expressions. Those regexes reject valid code -- for example the Digital Pet Game lab asserts /\s*enum\s+PetMood\s*{[\s*\w+,\s*]*HAPPY[\s*\w+,\s*]*} which matches `HAPPY,` but fails on `HAPPY = 'HAPPY',` because the character class excludes `=` and quotes. Adds the same treatment the other node kinds already receive: - `findMembers` returns `EnumDeclaration.members`, so `getAll()` can reach enum members - `enums` maps enum declarations by name, mirroring `classes`/`interfaces` - `enumMembers` maps members of a single enum, mirroring `methods` - `value` returns an enum member's initializer, or an empty `Explorer` - a new `enumMember` parse context so `matches()` works The parse context is required, not incidental: an `EnumMember` is neither a `TypeNode` nor an `Expression`, so it falls through every existing `CONTEXT_GUARDS` entry to `"source"` and gets compared against an `ExpressionStatement`, which never matches. Regular, `const` and exported enums are all `EnumDeclaration` statements, so all three are found. Members are keyed with `name.getText()` rather than the `(name as Identifier).text` cast used elsewhere, because `ComputedPropertyName` has no `text` property and would collapse onto a single bogus `undefined` key.

Commits

Commits on Sep 29, 2026

feat: add enum support to Explorer