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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@nestjs-automapper/typeorm

v2.0.1

Published

TypeORM schema adapter for @nestjs-automapper

Downloads

14

Readme

@nestjs-automapper/typeorm

TypeORM schema adapter. Lets a DTO derive its own select and relations.

pnpm add @nestjs-automapper/typeorm

Peer: typeorm ^1.1.1.

Usage

import { typeorm } from '@nestjs-automapper/typeorm';

const mapper = new Mapper().use(typeorm(dataSource));

That is the whole setup. Entities need no mapping decorators — the adapter reads the metadata TypeORM already has.

Projection

const find = mapper.nativeProjectionFor(ReadUserDto) as FindManyOptions<User>;
// { select: { id: true, email: true, firstName: true, lastName: true } }

await repo.find(find);

A twenty-column entity behind a five-field DTO issues a five-column SELECT. Relations the DTO never touches are not joined.

The primary key is added even when the DTO omits it — TypeORM needs it to hydrate relations and dedupe rows. That happens here rather than in core, so the neutral selection keeps reporting only what the DTO consumes.

What it reads

| TypeORM | Used for | |---|---| | column.propertyName | the field name, verbatim | | column.databaseName | translation and did-you-mean only | | column.type, enum | JSON/OpenAPI types and enum values | | isNullable | nullability, and OpenAPI required | | isPrimary, isGenerated | write drop list, projection keys | | isCreateDate, isUpdateDate, isDeleteDate | write drop list | | isVersion, isDiscriminator | write drop list | | isSelect | hidden on read — not a write drop reason | | relation.joinColumns, relationType | relations and foreign keys |

isSelect: false is the password case: excluded from implicit expansion, still nameable, and always writable. Treating it as database-owned would make it impossible to ever set one.

Notes

  • describe() returns everything the schema declares and applies no policy. Filtering is the planner's job.
  • supports() never throws, so adapter arbitration stays predictable.
  • Entity schemas defined as plain objects (rather than classes) are not supported; relations need a class target.
  • A string | null column needs an explicit type — TypeScript reflects the union as Object, which TypeORM cannot map. That is true of TypeORM generally, not something this adapter adds.

License

MIT