npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

thomassloboda-reflector

v1.1.1

Published

> TypeScript decorators for seamless DTO ↔ Entity mapping

Readme

Reflector

TypeScript decorators for seamless DTO ↔ Entity mapping

Quality Gate Status Coverage npm version npm downloads Stable CI Beta CI License: MIT

Reflector is a lightweight TypeScript library that lets you map between DTOs and Entities using decorators and runtime metadata. It’s designed for clean, maintainable code in Node.js and TypeScript projects.


Features

  • 🚀 Decorator-based mapping for DTOs and Entities
  • 🔄 Automatic, recursive property mapping (including arrays)
  • 🛡️ Only public properties are mapped
  • 🧩 Extensible for custom mapping logic
  • 📦 Zero runtime dependencies (except reflect-metadata)

Installation

npm install @thomassloboda/reflector reflect-metadata

[!IMPORTANT] You must enable experimentalDecorators and emitDecoratorMetadata in your tsconfig.json.

{
  "compilerOptions": {
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true
  }
}

Quick Start

import 'reflect-metadata';
import { Entity, EntityProperty } from '@thomassloboda/reflector';

@Entity(UserEntity)
class UserDTO {
  @EntityProperty('id')
  public id!: string;

  @EntityProperty('name')
  public name!: string;
}

const dto = new UserDTO();
dto.id = 'u123';
dto.name = 'Alice';

const entity = (dto as any).mapToEntity();
// entity: { id: 'u123', name: 'Alice' }

API Overview

Decorators

  • @Entity(EntityClass) — Attach mapping logic to a DTO
  • @EntityProperty('propertyName', { mapClass?: Class }) — Map a DTO property to an entity property

Methods

  • mapToEntity() — Map DTO to entity object
  • mapFromEntity(entity) — Populate DTO from entity object
  • getEntityMappings(target) — Get mapping metadata
  • mapToEntity<T, U>(dto, EntityClass, DtoClass) — Utility for manual mapping

Advanced Usage

  • Nested objects & arrays: Use mapClass to recursively map child DTOs
  • Type safety: Use TypeScript type assertions if needed
  • Custom logic: Extend DTOs/entities for custom mapping

FAQ & Tips

[!TIP] Always import reflect-metadata at the top of your entry file.

[!WARNING] Only public properties (with getters) are mapped. Private fields are ignored.

[!NOTE] The library is framework-agnostic and works with any Node.js/TypeScript project.


Useful Links


Enjoy clean, declarative mapping in your TypeScript projects!