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

@tresdoce/nestjs-httpclient

v0.1.2

Published

NestJS httpClient module

Downloads

89

Readme

Esta dependencia está pensada para ser utilizada en NestJs Starter, o cualquier proyecto que utilice una configuración centralizada, siguiendo la misma arquitectura del starter.

Glosario


📝 Requerimientos básicos

🛠️ Instalar dependencia

npm install @tresdoce/nestjs-httpclient

👨‍💻️ Uso

Importar HttpClientModule en el módulo que requiera utilizarlo, o bien se puede utilizarla de manera global en el app.module.ts.

// .src/app.module.ts

import { HttpClientModule } from '@tresdoce/nestjs-httpclient';

@Module({
  ...,
  imports: [
    ...,
  HttpClientModule,
  ...,
]
...,
})

export class AppModule {
}

Luego inyecte HttpClientService en el constructor de la clase que requiere realizar requests.

// ./src/app.service.ts

import { HttpClientService } from '@tresdoce/nestjs-httpclient';

export class AppService {
  constructor(private readonly httpClient: HttpClientService) {
  }
}

Realice el request utilizando el servicio instanciado en el constructor.

// ./src/app.service.ts
export class AppService {
...

  async getInfoFromApi() {
    try {
      const { status, data } = await this.httpClient.get('http://api.domain.com')
      return data;
    } catch (error) {
      return error;
    }
  }

...
}

⚙️ Configuración

Este módulo utiliza Axios y Axios-retry, por lo que puedes pasarle cualquier configuración de AxiosRequestConfig y/o AxiosRetryConfig por medio del método .register() como si fuera el httpModule original de NestJs.

import { HttpClientModule } from '@tresdoce/nestjs-httpclient';

@Module({
  imports: [
    HttpClientModule.register({
      timeout: 1000,
      retries: 5,
      ...
    }),
  ]
})

Configuración async

Cuando necesite pasar las opciones del módulo de forma asincrónica en lugar de estática, utilice el método .registerAsync() como si fuera el httpModule original de NestJs.

Hay varias formas para hacer esto.

  • useFactory

Desde la configuración centralizada, debera crear un objeto de configuración para el módulo, y luego obtenerlo con la inyección del ConfigService.

HttpClientModule.registerAsync({
  imports: [ConfigModule],
  useFactory: async (configService: ConfigService) => configService.get('config.httpOptions'),
  inject: [ConfigService]
});

O también puede hacerlo asi.

HttpClientModule.registerAsync({
  useFactory: () => ({
    timeout: 1000,
    retries: 5,
    ...
  })
});
  • useClass
HttpClientModule.registerAsync({
  useClass: HttpConfigService
});

Tenga en cuenta que en este ejemplo, el HttpConfigService tiene que implementar la interfaz HttpModuleOptionsFactory como se muestra a continuación.

@Injectable()
class HttpConfigService implements HttpModuleOptionsFactory {
  async createHttpOptions(): Promise<HttpModuleOptions> {
    const configurationData = await someAsyncMethod();
    return {
      timeout: configurationData.timeout,
      retries: 5,
      ...
    };
  }
}
  • useExisting

Si desea reutilizar un proveedor de opciones existente en lugar de crear una copia dentro del HttpClientModule, utilice la sintaxis useExisting.

HttpClientModule.registerAsync({
  imports: [ConfigModule],
  useExisting: ConfigService,
});

📤 Commits

Para los mensajes de commits se toma como referencia conventional commits.

<type>[optional scope]: <description>

[optional body]

[optional footer]
  • type: chore, docs, feat, fix, refactor (más comunes)
  • scope: indica la página, componente, funcionalidad
  • description: comienza en minúsculas y no debe superar los 72 caracteres.

📄 Changelog

All notable changes to this package will be documented in Changelog file.