Decorator metadata (TS 5.2). Every standard decorator on a class and its members receives the same context.metadata object. After the class is defined it is stored on Class[Symbol.metadata]. For a subclass, the object's prototype is the parent's metadata, so reads fall back to the parent while writes stay local. This replaces the reflect-metadata global registry with plain objects: a @column field decorator records names, and an ORM reads Model[Symbol.metadata].columns later. The tc39/proposals list puts it at Stage 2.7 while its README says Stage 3 (fetched 2026-10).
Runtime: Node 24.19 has no Symbol.metadata, and TypeScript's helper then passes undefined, so context.metadata.x throws a TypeError. Polyfill before any decorated class is evaluated. Types: lib must include esnext or esnext.decorators; without it context.metadata is typed DecoratorMetadataObject | undefined (TS18048).
accessor fields (TS 4.9). accessor status = "new" turns into a get/set pair on the prototype over a private #status_accessor_storage field. Field decorators only see the initial value (their value is undefined); an accessor decorator gets { get, set } and returns any of { get, set, init }, so it can observe or validate every write: signals, change tracking, validation. Node 24.19 cannot parse accessor either (SyntaxError), so TypeScript lowers it below --target esnext.
emitDecoratorMetadata (legacy). With experimentalDecorators (TS5052 without it), tsc adds __metadata("design:paramtypes", [...]) to decorated classes, plus design:type and design:returntype on members. These are runtime constructor references for erased types, so a container reading them through reflect-metadata knows which classes to new for a constructor. Interfaces, unions and type aliases become Object, so those dependencies need explicit tokens. Standard decorators do not support it. TypeScript 7.0.2 still accepts both legacy flags, with emit identical to 6.0.3.