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

@leocode/nest-tx-kysely

v1.0.0

Published

A Kysely connector for next-tx.

Downloads

8

Readme

nest-tx-kysely

A Kysely connector for next-tx.

Installation

Yarn:

yarn add next-tx-core nest-tx-kysely kysely

NPM:

npm install next-tx-core nest-tx-kysely kysely

Usage

Initialize the module first. Here we are using custom module for creating Kysely instance:

import { Module } from '@nestjs/common';
import { TransactionManager } from '@leocode/nest-tx-core';
import { KyselyTransactionManagerModule } from '@leocode/nest-tx-kysely';

@Module({})
export class KyselyModule {
  public static forRoot(options: { name: string; }): DynamicModule {
    const providers = [{
      provide: options.name,
      useFactory: () => {
        return new Kysely<unknown>({
          dialect: new PostgresDialect({
            pool: new Pool({
              host: 'localhost',
              port: 5432,
              user: 'postgres',
              password: 'secret',
              database: 'postgres',
            })
          })
        })
      },
    }];

    return {
      module: KyselyModule,
      providers: providers,
      exports: providers,
      global: true,
    }
  }
}

const KYSELY_INSTANCE_NAME = 'kysely__default';

@Module({
  imports: [
    KyselyModule.forRoot({
      name: KYSELY_INSTANCE_NAME,
    }),
    KyselyTransactionManagerModule.forRoot({
      // we need to provide an instance token
      // so the TX manager can get a Kysely instance from the DI container
      getInstanceToken: () => {
        return KYSELY_INSTANCE_NAME;
      },
    }),
  ],
})
class AppModule {}

Then you can use it in your services:

import { Injectable } from '@nestjs/common';
import { InjectTransactionManager, TransactionManager } from '@leocode/nest-tx-core';

interface TestTable {
  id: number;
}

interface Database {
  test: TestTable;
}

@Injectable()
class CatsService {
  constructor(
    @InjectTransactionManager() private readonly transactionManager: TransactionManager,
  ) {
  }

  public async save() {
    await this.transactionManager.withTransaction(async tx => {
      const kyselyTrx = tx.getKyselyTransaction<Database>();

      await kyselyTrx.selectFrom('test').selectAll().execute();
    });
  }
}