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

@entity-history/nestjs-typeorm

v0.2.0

Published

NestJS integration for @entity-history/typeorm

Readme

@entity-history/nestjs-typeorm

Renamed from nestjs-typeorm-history (deprecated on npm).

NestJS integration for @entity-history/typeorm: automatic user attribution per request, and DI-friendly history repositories.

Install

npm install @entity-history/nestjs-typeorm @entity-history/typeorm

Peer dependencies: @nestjs/common, @nestjs/core, @nestjs/typeorm (>= 10), rxjs (>= 7), typeorm (>= 0.3.20), and @entity-history/typeorm itself — it is a peer (not a regular dependency) so your app and this package always share the single copy whose registry and context the subscriber reads.

Usage

import { Module } from '@nestjs/common';
import { TypeOrmModule } from '@nestjs/typeorm';
import { historyEntities, HistorySubscriber } from '@entity-history/typeorm';
import { HistoryModule } from '@entity-history/nestjs-typeorm';
import { User } from './user.entity';

@Module({
  imports: [
    TypeOrmModule.forRoot({
      // ...
      entities: [User, ...historyEntities()],
      subscribers: [HistorySubscriber],
    }),
    HistoryModule.forRoot({
      userResolver: (ctx) => ctx.switchToHttp().getRequest().user?.id ?? null,
    }),
    HistoryModule.forFeature([User]),
  ],
})
export class AppModule {}
import { Injectable } from '@nestjs/common';
import { InjectHistoryRepository } from '@entity-history/nestjs-typeorm';
import { HistoryRepository } from '@entity-history/typeorm';
import { User } from './user.entity';

@Injectable()
export class UserService {
  constructor(@InjectHistoryRepository(User) private readonly userHistory: HistoryRepository<User>) {}

  async historyFor(userId: number) {
    return this.userHistory.forEntity(userId).all();
  }
}

HistoryModule.forRoot() installs a global interceptor that runs userResolver on every request and makes the resolved id available to @entity-history/typeorm's write path automatically — no extra code needed at the call site.

Multiple data sources

forFeature accepts the same data-source reference as @nestjs/typeorm (name, options object, or instance):

HistoryModule.forFeature([Metric], 'analytics');
// ...
constructor(@InjectHistoryRepository(Metric, 'analytics') private readonly metricHistory: HistoryRepository<Metric>) {}

Outside HTTP requests

Cron jobs, queue consumers, and scripts aren't covered by the interceptor. Use withHistoryContext from @entity-history/typeorm directly:

import { withHistoryContext } from '@entity-history/typeorm';

await withHistoryContext({ userId: 'system', changeReason: 'nightly sync' }, async () => {
  await userRepo.save(user);
});