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

@nathapp/nestjs-typeorm

v4.1.0

Published

@nathapp/nestjs-typeorm

Readme

@nathapp/nestjs-typeorm

TypeORM integration for NestJS, including named connections, custom repository wiring, stored procedure helpers, and transaction propagation.

Transactions

Enable transaction support when registering a connection:

TypeOrmExModule.forRoot({
  type: 'postgres',
  url: process.env.DATABASE_URL,
  entities: [UserEntity],
  transaction: true,
});

Inject TRANSACTION_MANAGER for the default connection or getTypeOrmTransactionManagerToken(name) for a named connection. Repository lookups through AbstractTypeOrmRepository, legacy @CustomRepository repositories, BaseSpRepository.callQuery, @Transactional, and TransactionService.withTransaction use the active runner for that DataSource. Each connection has an independent context, including during nested and concurrent work.

Stored procedure results

BaseSpRepository.callQuery preserves the driver result shape: PostgreSQL's flat rows form one recordset, and MySQL/MariaDB remove a trailing status packet only when the driver returned one. MySQL/MariaDB multiple recordsets remain arrays of recordsets. The optional rename callback applies to each row, and the objectifyForSignleRecord flag returns a single row as an object, multiple rows as an array, and an empty result as {}. Calls without a recordset return [] by default.