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

nestjs-consul

v1.5.1

Published

NestJS consul config Module

Downloads

239

Readme

NestJS consul config Module

alt cover

More NestJS libs on alariblog.ru Updated for NestJS 9

npm version npm version npm version npm version

NestJS consul package allows you to load configs from consul and work with key/values.

npm i nestjs-consul

Then register module in your root app.module

import { ConsulModule } from 'nestjs-consul';

@Module({
	imports: [
		// ...
		ConsulModule.forRoot <
			YourConfig >
			{
				keys: [{ key: 'your/keypath' }],
				updateCron: '* * * * *',
				connection: {
					protocol: 'http',
					port: 8500,
					host: '192.168.0.1',
					token: 'mutoken',
				},
			},
	],
})
export class AppModule {}

If you want to inject dependency into forRoot method like Configuration service, use forRootAsync:

import { ConsulModule } from 'nestjs-consul';

@Module({
	imports: [
		// ...
		ConfigModule,
		ConsulModule.forRootAsync({
			imports: [ConfigModule],
			inject: [ConfigService],
			useFactory: async (configService: ConfigService) => {
				return {
					keys: [{ key: 'am-cli/test' }],
					connection: {
						protocol: 'http',
						port: configService.getIP(),
						host: '192.168.0.1',
						token: 'admin',
					},
				};
			},
		}),
	],
})
export class AppModule {}
  • keys (IConsulKeys[]?) - array of keys and required status from which you want to load values. If key was not found and it was required, app with throw an exception. If it was not required - you will see warning. If no keys specified, no initial configs will be loaded.
  • updateCron (string) - cron string. If specified, will update configs on cron.
  • protocol ('http' | 'https') - consul protocol.
  • protocol ('http' | 'https') - consul protocol.
  • port (number) - consul port.
  • host (string) - consul host.
  • token (string) - consul auth token.
  • YourConfig (interface) - interface, that describes you entire config. This will allow you to use type save configs. In this example it would be like:
export interface YourConfig {
	'your/keypath': {
		value1: number,
		value2: string,
	};
}

Then you can use your configs with public property configs of ConsuleService.

import { ConsuleService } from 'nestjs-consul';

constructor(
	private readonly consul: ConsuleService
) {}

myMethod() {
    const configs = this.consul.configs;
}

Additional methods

update()

Returns Promise<void>. Force updates your config.

await this.consul.update();

get(key: string)

Returns Promise<T>. Gets a value from consul with key and T type.

const value = (await this.consul.get) < MyInterface > 'my/key';

set(key: string, value: T)

Returns Promise<boolean>. Sets a value to consul with key and T type. Returns true if succeeded.

const response = (await this.consul.set) < MyInterface > ('my/key', value);

delete(key: string)

Returns Promise<boolean>. Deletes a value from consul with key. Returns true if succeeded.

const response = await this.consul.delete('my/key');

Running tests

To run e2e tests you need to have consul instance started and run test for the firs time (to add config key).

Then run tests with.

npm run test

alt cover