promise implementation of nestjs http module with retries feature using axios-retry and axios. 

promise implementation of nestjs http module with retries feature using axios-retry and axios

benhas1

nestjs-http-promise

Error

Ignore

Warn

License

Maintenance

Miscellaneous

Quality

Supply chain risk

Vulnerability

Admins only

Organization members

Dashboard

<upgradeLink>Upgrade</upgradeLink> to access this feature

About

Blog

Socket CLI

Customers

Socket Dependency Search

Docs

Socket for GitHub

Love

Impersonation Mode Active

Update your browser to the latest version for the best experience.

Your web browser is outdated

Use another browser for the best experience.

Your web browser is unsupported

{{count, number}} commits last two months

{{count, number}} critical severity alert

{{count, number}} critical severity alerts

{{count, number}} dependency vulnerability

{{count, number}} dependency vulnerabilities

{{count, number}} development dependencies

{{count, number}} transitive dependencies

{{count, number}} version published last month

{{count, number}} versions published last month

{{count, number}} version published in last two months

{{count, number}} versions published in last two months

{{count, number}} version published last week

{{count, number}} versions published last week

{{count, number}} version published last year

{{count, number}} versions published last year

Socket undergoes annual SOC2 Type II audits. Socket customers can request a copy of the full SOC2 Type II report.

Allows organization owners and admins to access detailed records of actions taken by members of their organization, complete with timestamps.

Prevent compromised packages from infiltrating your supply chain by monitoring for changes in real-time.

Join our Discord community to get help from Socket engineers and other Socket users.

Compare millions of open source packages on socket.dev

Detect malicious code and risky behavior (e.g. network) in your dependencies using "deep package inspection"

All data is encrypted in transit and at rest using industry standard encryption algorithms.

Get a dedicated Socket account manager and access to Socket’s Customer Success team.

Get dedicated support from Socket engineers via email and Slack.

"Shift left" with the Socket Chrome extension and give intervene early, before developers choose risky or low quality dependencies.

Catch developers using risky dependencies and give them a "speed bump" to encourage good behavior

Install the Socket GitHub app to receive real-time dependency scanning and reports with every pull request.

Integrate Socket into your GitHub SCM to prevent risky dependencies from being installed.

Socket scans for vulnerabilities in your dependencies, including CVEs, security advisories, and more.

Socket supports dependencies in many languages, with most popular ecosystems coming in 2024. We've got you covered no matter what languages you use.

Enforce license policies across your organization

Receive a Microsoft Teams message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Get help migrating from Socket's free plan to Socket's paid plans.

Run Socket on-premises or in your own cloud environment.

Query for any dependency (at any version) across your entire organization

Integrate Socket into your CI/CD pipeline to prevent risky dependencies from being deployed to production.

Analyze an entire project to find supply chain risks

Tag projects to organize and filter your projects

Restrict access based on the roles of individual users within an organization.

Receive a Slack message to the channel of your choice anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket is SOC2 Type II compliant and undergoes annual audits.

The Socket CLI allows teams to prevent risky dependencies from being installed, and to get dependency insights from the command line.

Socket supports SAML SSO for single sign-on and identity management.

Integrate Socket into your VS Code IDE to prevent risky dependencies from being installed.

Get a POST request anytime Socket runs a new analysis, has a new finding, or a policy has changed.

Socket will analyzed your SBOMs up to a maximum number of dependencies.

API that allows you to analyze a project, lookup package scores and alerts, and more.

Create API tokens to authenticate with the Socket API and CLI.

The number of developers in your team. A developer is someone who made a commit to your organization's repositories scanned by Socket in the past month.

Use Socket to protect your private repositories.

Socket is always free for open source projects.

Socket retains all reporting data for 3 months, 1 year, or a custom term of your choice.

Access the threat feed that powers Socket.

Unlimited scale, self-hosting, and priority support for large teams.

For open-source projects, individuals, and small teams.

For growing teams with enhanced scale, security, and support.

There is a package with a similar name that is downloaded much more often.

There are packages with similar names that are downloaded much more often.

This may not be the package you want!

Instance

Alert Locations

Package

The {{ecosystem}} package {{- packageName}} receives a total of <strong>{{numWeeklyDownloadCount, number}}</strong> weekly downloads. As such, {{- packageName}} popularity was classified as <strong>{{popularity}}</strong>.

Is {{- packageName}} popular?

Is {{- packageName}} safe to use?

Is {{- packageName}} well maintained?

What is {{- packageName}}?

{{packageDescription}}Version: {{versionString}} was published by {{publisherName}}. Start using Socket to analyze {{- packageName}} and its {{dependencyCount, number}} dependencies to secure your app from supply chain attacks.

Sorry, it seems this package was removed from the registry

Package was removed

This package version has been unpublished, mostly likely due to security reasons

Package version was removed

Provide a detailed description of the malware...

Socket fights vulnerabilities and provides visibility, defense-in-depth, and proactive supply chain protection for JavaScript, Python, and Go dependencies.

Socket - Secure your dependencies. Ship with confidence.

Compare versions

{{- packageName}} - npm Package Compare versions

  "description": "promise implementation of nestjs http module with retries feature using axios-retry and axios",

  "url": "https://github.com/benhason1/nestjs-http-promise#readme",

    "build": "rimraf -rf dist && tsc -p tsconfig.json",

    "format": "prettier --write \"{lib}/**/*.ts\"",

    "lint": "eslint 'lib/**/*.ts' --fix",

    "publish:npm": "npm publish --access public",

    "publish:beta": "npm publish --access public --tag beta",

    "@typescript-eslint/eslint-plugin": "4.30.0",

    "@typescript-eslint/parser": "4.30.0",

    "@nestjs/common": "^7.0.0 || ^8.0.0",

    "url": "https://github.com/benhason1/nestjs-http-promise"

[![npm version](https://img.shields.io/npm/v/nestjs-http-promise.svg?style=flat-square)](https://www.npmjs.org/package/nestjs-http-promise)

nestjs module that just doing little modification to the original and good **nestjs** http module.

  * axios - the most used package for http requests in npm.

  * promise based - most of us using the current http module and on every call do `.toPromise()`

    because most of the time we do not need the features of observable.

  * retries - one of the powerful features of observable is its ability to do in very simple way,

    you can do it by just adding the retry operator, this package will provide you the same feature even in easier way,

    just pass `{ retries: NUMBER_OF_RETRIES }` in the config of the http module.

  * promise based - most of us using the current http module that uses observable which we don't use most of the time 

    and in order to avoid it were just calling `.toPromise()` every http call.

  * retries - in many cases we will want to retry a failing http call.

    with observable we could just add the retry operator (rxjs) but with promises we need to implement this logic ourselves.

    this package will make it easy for you, just pass `{ retries: NUMBER_OF_RETRIES }` in the config of the http module.

    **more details in the configuration section**

### usage - just like every nest.js module

import { HttpModule } from 'nestjs-http-promise'

import { HttpService } from 'nestjs-http-promise'

    constructor(private readonly httpService: HttpService) {}

public callSomeServer(): Promise<object> {

  return this.httpService.get('http://fakeService') 

the service uses axios and axios-retry, so you can pass any [AxiosRequestConfig](https://github.com/axios/axios#request-config)

And/Or [AxiosRetryConfig](https://github.com/softonic/axios-retry#options)

just pass it in the `.register()` method as you would do in the original nestjs httpModule

 just the default config of axios-retry : https://github.com/softonic/axios-retry#options

When you need to pass module options asynchronously instead of statically, use the `registerAsync()` method **just like in nest httpModule**.

you have a couple of techniques to do it:

Note that in this example, the HttpConfigService has to implement HttpModuleOptionsFactory interface as shown below.

class HttpConfigService implements HttpModuleOptionsFactory {

  async createHttpOptions(): Promise<HttpModuleOptions> {

    const configurationData = await sonmeAsyncMethod();

    const configurationData = await someAsyncMethod();

      timeout: configurationData.timeout,

If you want to reuse an existing options provider instead of creating a copy inside the HttpModule, 

		{
		"name": "nestjs-http-promise",
		"version": "1.0.0",
		"version": "1.0.1",
		"keywords": [
		@@ -5,0 +5,0 @@ "nestjs",

Improved metrics

Worsened metrics

		# nestjs-http-promise
		[![npm version](https://img.shields.io/npm/v/nestjs-http-promise.svg?style=flat-square)](https://www.npmjs.org/package/nestjs-http-promise)

		@@ -9,7 +10,9 @@ ## description
		* axios - the most used package for http requests in npm.
		* promise based - most of us using the current http module and on every call do `.toPromise()`
		because most of the time we do not need the features of observable.
		* retries - one of the powerful features of observable is its ability to do in very simple way,
		you can do it by just adding the retry operator, this package will provide you the same feature even in easier way,
		just pass `{ retries: NUMBER_OF_RETRIES }` in the config of the http module.
		* promise based - most of us using the current http module that uses observable which we don't use most of the time
		and in order to avoid it were just calling `.toPromise()` every http call.
		* retries - in many cases we will want to retry a failing http call.
		with observable we could just add the retry operator (rxjs) but with promises we need to implement this logic ourselves.
		this package will make it easy for you, just pass `{ retries: NUMBER_OF_RETRIES }` in the config of the http module.
		more details in the configuration section

		## quick start
		@@ -53,3 +56,3 @@ ### installing

		##configuration
		## configuration

		@@ -104,3 +107,3 @@ the service uses axios and axios-retry, so you can pass any [AxiosRequestConfig](https://github.com/axios/axios#request-config)
		async createHttpOptions(): Promise<HttpModuleOptions> {
		const configurationData = await sonmeAsyncMethod();
		const configurationData = await someAsyncMethod();
		return {
		@@ -121,2 +124,2 @@ timeout: configurationData.timeout,
		});
		```
		```