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

@d3vtool/automapper

v1.2.2

Published

AutoMapper

Readme

🔄 AutoMapper Utility

AutoMapper is a lightweight TypeScript utility designed to automate the transformation of objects between DTOs and Entities. It simplifies mapping between classes with matching or custom field names, keeping data transformation code clean and maintainable.

In addition to object mapping, it also supports decorator-based DTO validation at instantiation time, allowing you to enforce field-level rules such as @Required, @Email, @StringLength, and more. Validation errors throw a clear ValidationFailedError with the field name and message.

Includes a JsonObject base class for easily converting class instances to and from plain object literals (JSON-compatible structures).


Table of Contents


📦 Installation

Install via your preferred package manager:

npm

npm install @d3vtool/automapper

yarn

yarn add @d3vtool/automapper

✅ Testing

To run the tests:

npm run test

✨ Features

  • Automatic mapping of fields between objects with matching names.

  • Explicit mapping support for different field names using forMember().

  • Allows multiple mapping configurations (e.g., User to UserDto and UserDto to User).

  • JSON serialization and deserialization using the JsonObject base class.

  • DTO decorator-based validation — enforce rules at instantiation time with built-in and custom validators.

  • Built-in decorators:

    • @Required() – enforce presence of a value.
    • @StringLength() – set minimum/maximum string length.
    • @Email() – validate RFC-compliant email addresses.
    • @Password() – validate password strength.
    • @Regex() – validate values against a regular expression.
    • @CustomFn() – run custom validation logic.
  • Automatic error handling via ValidationFailedError with .field and .message for failed validations.


🧪 Examples

🔹 JsonObject Usage

1. Convert JSON to Entity

import { JsonObject } from "@d3vtool/automapper";

class User extends JsonObject<User> {
  constructor(
    public id?: string,
    public name?: string,
    public email?: string,
    public password?: string
  ) {
    super();
  }
}

const user = new User();
user.fromJson({
  id: "12",
  name: "Alice",
  email: "[email protected]",
  password: "secure123"
});

console.log(user.name); // "Alice"

2. Convert Entity to JSON

const user = new User("12", "Alice", "[email protected]", "secure123");
const json = user.toJson();

console.log(json);
// { id: '12', name: 'Alice', email: '[email protected]', password: 'secure123' }

🔹 AutoMapper Usage

1. Create autoMapper instance

To create and reuse the AutoMapper instance:

import { AutoMapper } from "@d3vtool/automapper";

// Create one instance and reuse it across your application.
export const autoMapper = new AutoMapper();

2. Map with Matching Field Names (One Direction)

import { autoMapper } from "./somefile";
import { JsonObject } from "@d3vtool/automapper";

class User extends JsonObject<User> {
  constructor(
    public id?: string,
    public name?: string,
    public email?: string,
    public password?: string
  ) {
    super();
  }
}

class UserDto extends JsonObject<UserDto> {
  constructor(
    public id?: string,
    public name?: string,
    public email?: string
  ) {
    super();
  }
}

const userToDtoMapper = autoMapper.map(User, UserDto);

const user = new User("12", "Alice", "[email protected]", "secure123");
const userDto = userToDtoMapper.map(user);

console.log(userDto);
// Output: UserDto { id: '12', name: 'Alice', email: '[email protected]' }

3. Custom Mapping with Different Field Names

class User extends JsonObject<User> {
  constructor(
    public id?: string,
    public firstName?: string,
    public lastName?: string,
    public email?: string,
    public password?: string
  ) {
    super();
  }
}

class UserDto extends JsonObject<UserDto> {
  constructor(
    public id?: string,
    public fullName?: string,
    public email?: string
  ) {
    super();
  }
}

const userToDtoMapper = autoMapper.map(User, UserDto);

// Custom mapping for `fullName` (combining `firstName` + `lastName`)
userToDtoMapper.forMember("fullName", (user) => `${user.firstName} ${user.lastName}`);

const user = new User("12", "Alice", "Smith", "[email protected]", "secure123");
const userDto = userToDtoMapper.map(user);

console.log(userDto);
// Output: UserDto { id: '12', fullName: 'Alice Smith', email: '[email protected]' }

4. Explicit Reverse Mapping (UserDto to User)

To map in the reverse direction, you must explicitly create a new mapping:

const dtoToUserMapper = autoMapper.map(UserDto, User);

// Assuming userDto is an instance of UserDto and fields are same of entity and dto.
const userFromDto = dtoToUserMapper.map(userDto);

// If fields aren't same then:
dtoToUserMapper
    .forMember("firstName", (dto) => dto.fullName?.split(" ")[0])
    .forMember("lastName", (dto) => dto.fullName?.split(" ")[1]);

const userFromDto = dtoToUserMapper.map(userDto);

console.log(userFromDto);
// Output: User { id: '12', firstName: 'Alice', lastName: 'Smith', email: '[email protected]', password: 'secure123' }

DTO Validation Decorators Usage

The @DTO decorator, in combination with field-level validation decorators, allows you to enforce rules at instantiation time. If validation fails, ValidationFailedError is thrown with the invalid field and a descriptive message.

Note: To use decorators in TypeScript, you must enable the experimental feature in your tsconfig.json:

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

All decorators (except StringLength) accept an optional final parameter:

errorMsg?: string // Custom error message for this validation rule

1. @Required()

Marks a field as mandatory. Missing or empty values will cause validation to fail.

@DTO
class User extends JsonObject<User> {
  constructor(
    @Required("Name is required")
    public name?: string
  ) {
    super();
  }
}

// ✅ Passes
new User("Alice");

// ❌ Fails
try {
  new User();
} catch (err) {
  console.log(err instanceof ValidationFailedError); // true
  console.log(err.field); // "name"
  console.log(err.message); // "Name is required"
}

2. @StringLength(minLength, maxLength?, errorMsg?: StringLengthParamError)

Enforces string length limits. You can provide different error messages for minLength and maxLength failures.

@DTO
class User extends JsonObject<User> {
  constructor(
    @StringLength(5, 10, {
      minLength: "Name must be at least 5 characters",
      maxLength: "Name must be no more than 10 characters"
    })
    public name?: string
  ) {
    super();
  }
}

// ✅ Passes
new User("Alice");

// ❌ Too short
try {
  new User("Al");
} catch (err) {
  console.log(err.field); // "name"
  console.log(err.message); // "Name must be at least 5 characters"
}

// ❌ Too long
try {
  new User("AlexandriaTheGreat");
} catch (err) {
  console.log(err.field); // "name"
  console.log(err.message); // "Name must be no more than 10 characters"
}

3. @Email()

Validates that the field contains a valid RFC-compliant email address.

@DTO
class User extends JsonObject<User> {
  constructor(
    @Email("Invalid email address")
    public email?: string
  ) {
    super();
  }
}

// ✅ Passes
new User("[email protected]");

// ❌ Invalid
try {
  new User("invalid-email");
} catch (err) {
  console.log(err.field); // "email"
  console.log(err.message); // "Invalid email address"
}

4. @Password()

Validates password strength (implementation-dependent, e.g., min length, uppercase, number, symbol).

@DTO
class User extends JsonObject<User> {
  constructor(
    @Password("Password is too weak")
    public password?: string
  ) {
    super();
  }
}

// ✅ Passes
new User("Aa1!aaaa");

// ❌ Too weak
try {
  new User("123");
} catch (err) {
  console.log(err.field); // "password"
  console.log(err.message); // "Password is too weak"
}

5. @Regex(pattern: RegExp, errorMsg?: string)

Validates that the string matches a given pattern. Example: Austrian phone numbers starting with +43.

@DTO
class User extends JsonObject<User> {
  constructor(
    @Regex(/^\+43\s?(\d[\s-]?){4,14}$/, "Invalid Austrian phone number")
    public phone?: string
  ) {
    super();
  }
}

// ✅ Passes
new User("+43 123-456-789");

// ❌ Invalid
try {
  new User("0043 123456");
} catch (err) {
  console.log(err.field); // "phone"
  console.log(err.message); // "Invalid Austrian phone number"
}

6. @CustomFn(validatorFn: (value: unknown) => true | string, errorMsg?: string)

Runs a custom validation function. If it returns true, validation passes. If it returns a string, that string is used as the error message.

/**
 * Custom field validation function.
 *
 * Parameters:
 * - `value`: The data for the current field being validated.
 * - `body` : The entire payload passed to the constructor.
 *
 * Notes:
 * - `body` can be used to perform cross-field validations and more.
 */
export type CustomFn<T = unknown> = (value: T, body?: unknown) => boolean | ErrorString;
@DTO
class User extends JsonObject<User> {
  constructor(
    @CustomFn((value) => {
      if (typeof value !== "string") return "Date must be a string";
      const parts = value.split("/");
      if (parts.length !== 3) return "Invalid date format";

      const [dd, mm, yyyy] = parts.map(Number);
      const daysInMonth = new Date(yyyy, mm, 0).getDate();

      if (yyyy < 1900 || yyyy > new Date().getFullYear()) return "Invalid year";
      if (mm < 1 || mm > 12) return "Invalid month";
      if (dd < 1 || dd > daysInMonth) return "Invalid day";

      return true;
    })
    public birthDate?: string
  ) {
    super();
  }
}

// ✅ Passes
new User("01/01/2000");

// ❌ Invalid
try {
  new User("32/01/2000");
} catch (err) {
  console.log(err.field); // "birthDate"
  console.log(err.message); // "Invalid day"
}
// Referencing example 
@DTO
class User extends JsonObject<User> {
    constructor(
        @Required()
        @StringLength(4)
        public password?: string,

        @CustomFn((value: unknown, body?: unknown) => {

            const userBody = body as any;
            const confirmPassword = value as string;

            if (typeof confirmPassword !== 'string') {
                return "Invalid confirm password field data.";
            }

            if (userBody?.password !== confirmPassword) {
                return "Confirm Password and Password do not match.";
            }

            return true;
        })
        public confirmPassword?: string
    ) {
        super();
    }
}

new User("password", "password"); // ✅ Passes

try {

  new User("password", "differentPassword"); // ❌ will fail.

} catch(err: unknown) {
  if(err instanceof ValidationFailedError) {
    console.log(err.field, err.message);
  }
}


/**
 * Note:
 *  - Always wrap your constructor with try-catch
*/

Error Types

  1. ValidationFailedError Thrown when a validation rule fails. Has:

    • field: the name of the invalid field
    • message: the error message
  2. Native Error Also thrown when a value does not meet validator constraints.

    • For example, in StringLength(min, max), if max < min, an error will be thrown with a descriptive message.

This package is open-source and licensed under the MIT License.