reflect-metadata VS typescript-needs-types

We could use the reflect-metadata library to store the metadata and then scan it manually to replace the placeholders with actual values, but there is a better way.

Second, TypeScript 5.0 cannot emit decorator metadata. Subsequently, it doesn’t integrate with the Reflect API and won’t work with the reflect-metadata npm package.

Database columns will be mapped to domain object properties using decorators. This will include relationships and enum types. reflect-metadata stores metadata about the classes and properties. Most of the work is a simple map for each class, renaming db column properties to domain model properties and vice versa. Reflect.defineProperty holds a list of field metadata on the target class. This is where more database ORM logic could live in the future such as column type, length, etc. A base domain model entity will use this metadata to map the models appropriately.

Welcome to the list: https://www.typescriptneedstypes.com/

Lol, look what I just found, someone created a whole petition about adding runtime type information (which would make a lot of use libraries redundant): https://www.typescriptneedstypes.com/

Author of TypeBox here. myzod looks great :) There are a surprising amount of projects emerging nowadays in this space, but I rarely get a chance to converse with other authors. I see your project is on THE LIST too https://github.com/akutruff/typescript-needs-types :)