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-mikroorm

v0.1.0

Published

NestJS integration for @entity-history/mikroorm

Readme

@entity-history/nestjs-mikroorm

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

Install

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

Peer dependencies: @nestjs/common, @nestjs/core (>= 10), @mikro-orm/core, @mikro-orm/nestjs (>= 7), rxjs (>= 7), and @entity-history/mikroorm 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.

Setup

import { MikroOrmModule } from '@mikro-orm/nestjs';
import { historyEntities, HistorySubscriber } from '@entity-history/mikroorm';
import { HistoryModule } from '@entity-history/nestjs-mikroorm';

@Module({
  imports: [
    MikroOrmModule.forRoot({
      // ...driver config
      entities: [User, ...historyEntities()],
      subscribers: [new HistorySubscriber()],
    }),
    HistoryModule.forRoot({
      userResolver: (ctx) => ctx.switchToHttp().getRequest().user?.id ?? null,
    }),
    HistoryModule.forFeature([User]),
  ],
})
export class AppModule {}

HistoryModule.forRoot() installs a global interceptor that runs userResolver per request and attributes every history row written during that request to the resolved user. forFeature([Entity], contextName?) provides an injectable HistoryRepository per entity; pass a contextName for non-default MikroORM instances.

Usage

import { InjectHistoryRepository } from '@entity-history/nestjs-mikroorm';
import { HistoryRepository } from '@entity-history/mikroorm';

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

  findHistory(id: number) {
    return this.history.forEntity(id).all();
  }
}

Outside HTTP requests

Cron jobs, queue consumers, and scripts aren't covered by the interceptor. Use the context API directly:

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

await withHistoryContext({ userId: 'system', changeReason: 'nightly sync' }, () => em.flush());