Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

nest-memory-transport

Package Overview
Dependencies
Maintainers
0
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

nest-memory-transport

An in-memory (fake) transport strategy for NestJS microservices, useful for in-process integrative tests

  • 1.0.3
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
5
increased by400%
Maintainers
0
Weekly downloads
 
Created
Source

NestJS Memory Transport

This package aims to replace existing NestJS transport layers with a memory-based implementation. This is useful for testing purposes, as it allows you to run your application in memory without the need for a network connection. Specifically, it allows you to write in-process acceptance tests for a monorepo that consists of multiple microservices, without going out of process.

Installation

$ npm install nest-memory-transport

Getting Started

In order to replace existing transports such as Kafka or TCP, you'll need to restructure your NestJS application to allow injection of the transport layer from the outside.

Server

Assuming that your init code looks something like this:

async function bootstrap() {
  const app = await NestFactory.createMicroservice<MicroserviceOptions>(
    MyMicroserviceModule,
    {
      transport: Transport.KAFKA,
      options: {
        client: {
          clientId: 'some-client-id',
          brokers: ['localhost:9092'],
        },
        consumer: {
          groupId: 'some-consumer',
        },
      },
    },
  );
  await app.listen();
}
bootstrap();

with this:

// app.ts
export async function bootstrap(transportOptions: MicroserviceOptions) {
  const app = await NestFactory.createMicroservice<MicroserviceOptions>(
    MyMicroserviceModule,
    transportOptions,
  );
  await app.listen();
}

// main.ts
bootstrap({
  transport: Transport.KAFKA,
  options: {
    client: {
      clientId: 'some-client-id',
      brokers: ['localhost:9092'],
    },
    consumer: {
      groupId: 'some-consumer',
    },
  },
});

Then in your test, initialize the same microservice with the memory transport:

const emitter = new EventEmitter();
const myMicroService = await bootstrap({
  strategy: new MemoryTransportServer(emitter)
});

Client

Convert your AppModule to a DynamicModule that takes the transport layer as a parameter:

export class AppModule {
  static register(transport: DynamicModule): DynamicModule {
    return {
      imports: [transport, ...any other imports],
      controllers: [...your controllers],
      providers: [...your providers],
      module: AppModule,
    };
  }
}

In your main.ts, initialize the app with the production transport:

export async function bootstrap() {
  const app = await NestFactory.create(
    AppModule.register(
      ClientsModule.register([
        {
          name: 'KAFKA_CLIENT',
          transport: Transport.KAFKA,
          options: {
            client: {
              clientId: 'some-client-id',
              brokers: ['localhost:9092'],
            },
            consumer: {
              groupId: 'some-consumer',
            },
          },
        },
      ]),
    ),
  );
  await app.listen(3000);
  return app;
}

Then in your test, initialize the same app with the memory transport:

const appTestingModule = await Test.createTestingModule({ 
  imports: [AppModule.register(MemoryClientsModule.register({
    name: 'KAFKA_CLIENT',
    emitter, // the same emitter declared earlier, shared between all microservices and their clients
  }))],
}).compile();
await appTestingModule.createNestApplication().init();

See the e2e test for a full working example.

Issues

Ideally, add a failing test to any issue you submit.

Contributing

If you wish to contribute, please open a PR with a failing test, then implement the feature and make the test pass.

Keywords

FAQs

Package last updated on 13 Aug 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc