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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@takeny1998/nestjs-prisma-transactional

v1.0.5

Published

handling transaction with decorator in the nest.js and PrismaORM environments

Downloads

297

Readme

nestjs-prisma-transactional

Manage PrismaORM transactions easily by adding decorator to your nest.js services.

npm npm MIT License

Installation

Install with npm

  npm install @takeny1998/nestjs-prisma-transactional

Or install via yarn

  yarn add @takeny1998/nestjs-prisma-transactional

Usage

Step 1: Import Transaction Module

Import the TransactionMoudle to AppModule of your nest.js project. Or just add it to the module you want to use.

import { TransactionModule } from '@takeny1998/nestjs-prisma-transactional';

@Module({
  imports: [
    ...
    TransactionModule, // just import it
  ],
  controllers: [...],
  providers: [...],
})
export class AppModule {}

Step 2: Extend PrismaClient

I provide the extension so that you can freely extend PrismaClient. My extension does not modify the type of the existing PrismaClient, so you can simply extend and inject your own Client.

import { TransactionModule } from '@takeny1998/nestjs-prisma-transactional';

@Module({
  imports: [
    ...
    TransactionModule,
  ],
  controllers: [...],
  providers: [
    {
      provide: 'PrismaService',
      useValue: new PrismaService().$extends(txExtension),
    },
  ],
  exports: ['PrismaService'],
})
export class AppModule {}

Otherwise, a good alternative is to use the CustomPrismaModule from the nestjs-prisma package. (If you have a great way to extend PrismaClient, please let me know it by opening an issue)

Step 3: Add @Transactional Decorator whereever you want

Add the @Transactional() decorator to any method you want to make transactional scope, and all repositories using the method's child PrismaClient will automatically be merged as one transaction.


@Transactional()
async writePost(dto: WritePostDto) {
  const createdPost = await this.postService.createPost(userUuid, { ...post, summary });

  const user = await this.userService.findUserByUniqueInput({ uuid: userUuid });

  if (!user) {
    throw new NotFoundException(`Cloud not found User with UUID: ${userUuid}`);
  }

  ...
}

Even if there are decorators from repositories or domain services under the method, they will be merged into the top-level transaction scope.

Contributing

Contributions are always welcome!

If you have any suggestions for improvements or encounter a bug while using this package, please feel free to open an issue.