Neoclassic Placebo Maker

    TypeScript icon, indicating that this package has built-in type declarations

    3.1.4 • Public • Published

    travis npm downloads bundlephobia license coveralls Greenkeeper

    NestJSX Automapper

    A wrapper around @nartc/automapper to be used with NestJS as a Module.


    Migrate to v3

    forRoot() method will be deprecated soon (still available in v3). Please use withMapper() instead.


    This module is a wrapper around @nartc/automapper so all usage documentations should be referenced at the link below.

    Github Pages Github Repo


    • Mapping between two classes
    • Mapping for nested classes
    • Array/List Mapping
    • Flattening
    • Basic ReverseMap
    • Value Converters
    • Value Resolvers
    • Async
    • Before/After Callback
    • Naming Conventions (PascalCase and camelCase)

    Contributions are appreciated.


    npm i -s nestjsx-automapper

    Installing nestjsx-automapper will also install @nartc/automapper.

    Note 1: Please make sure that you've read @nartc/automapper documentations to familiarize yourself with AutoMapper's terminology and how to setup your Profile and such.


    1. Import AutomapperModule in AppModule and call .withMapper() method
      imports: [AutomapperModule.withMapper()],
    export class AppModule {}

    AutomapperModule.withMapper() has the following overloads:

    static withMapper(name?: string, options?: AutoMapperGlobalSettings);
    static withMapper(options?: AutoMapperGlobalSettings);
    • name: Name of the AutoMapper instance being created with withMapper(). Default to "default"
    • options: Check AutoMapperGlobalSettings for more information
    1. nestjsx-automapper exposes a @Profile() decorator to decorate your Profile classes.
    class UserProfile extends ProfileBase {}

    @Profile() takes in an optional name argument. This is the name if the AutoMapper instance you use to create the instance with withMapper(). Default to "default"

    Usually, NestJS will have many Feature Modules for each of the Domain Models. Hence, a Profile should stay in close to where the feature module is. If you want to separate Profile out to a separate file, then you need to make sure that file gets executed by importing it somewhere (again, the module is a good place).

    1. Inject the AutoMapper instance in your Injectable
    export class UserService {
      constructor(@InjectMapper() private readonly mapper: AutoMapper) {}

    @InjectMapper() takes in an optional name argument which will tell the decorator which AutoMapper instance to inject. Default to "default"

    InjectMapper is imported from nestjsx-automapper. AutoMapper is imported from @nartc/automapper

    1. Use AutoMapper on your models
    // ...
    const result = await;
    return, UserVm, User);


    npm i nestjsx-automapper

    DownloadsWeekly Downloads






    Unpacked Size

    32.7 kB

    Total Files


    Last publish


    • nartc