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-fetch

v0.1.0

Published

Fetch API as a NestJS provider

Downloads

330

Readme

nestjs-fetch

A lightweight NestJS wrapper around the native fetch() API.

The Fetch API is awesome, but until recently we have needed a library to use it with Node. As of Node 18, Fetch is available by default (based on the undici library). Hurrah! This library wraps a small API around native fetch() so it can be used in NestJS instead of @nestjs/axios.

Note: This is not a drop-in replacement for @nestjs/axios or the HttpModule. It has a completely different API.

Installation

npm install nestjs-fetch

Usage

Import the FetchModule in your application module.

import { Module } from '@nestjs/common';
import { AppController } from './app.controller';
import { AppService } from './app.service';
import { FetchModule } from 'nestjs-fetch';

@Module({
	imports: [FetchModule],
	controllers: [AppController],
	providers: [AppService],
})
export class AppModule {}

The FetchService is now available as a provider in your application.

import { Injectable } from '@nestjs/common';
import { FetchService } from 'nestjs-fetch';

@Injectable()
export class AppService {
	constructor(private readonly fetch: FetchService) {}

	async getExample(): Promise<string> {
		const response = await this.fetch.get('http://example.com/');
		return response.text();
	}
}

API

The public API presents six helper methods for making HTTP requests. The first argument to each method is a URL (either a URL object or a string); the second argument is an optional list of configuration options.

Each of these helpers returns a Response object. This Response object is documented over on MDN. You will probably want to await response.json() or response.text() to retrieve the body content.

interface FetchService {
	get(url: URL | string, options?: FetchModuleOptions): Promise<Response>;
	head(url: URL | string, options?: FetchModuleOptions): Promise<Response>;
	post(url: URL | string, options?: FetchModuleOptions): Promise<Response>;
	put(url: URL | string, options?: FetchModuleOptions): Promise<Response>;
	patch(url: URL | string, options?: FetchModuleOptions): Promise<Response>;
	delete(url: URL | string, options?: FetchModuleOptions): Promise<Response>;
}

FetchModuleOptions includes all the options you can send to a Request object, plus one additional option: baseUrl. If you supply a relative URL as the argument to the FetchService then it will be resolved against the baseUrl.

Configuration with Nest

Set up as a provider in your app module:

import { Module } from '@nestjs/common';
import { AppController } from './app.controller';
import { AppService } from './app.service';
import { FetchModule } from 'nestjs-fetch';

@Module({
	imports: [FetchModule.register({ baseUrl: 'http://example.com' })],
	controllers: [AppController],
	providers: [AppService],
})
export class AppModule {}

Async set up is also supported.

import { Module } from '@nestjs/common';
import { AppController } from './app.controller';
import { AppService } from './app.service';
import { FetchModule } from 'nestjs-fetch';
import { ConfigModule, ConfigService } from '@nestjs/config';

@Module({
	imports: [
		ConfigModule.forRoot({ isGlobal: true }),
		FetchModule.registerAsync({
			inject: [ConfigService],
			useFactory(config: ConfigService) {
				return { keepalive: config.get('ENABLE_KEEPALIVE') };
			},
		}),
	],
	controllers: [AppController],
	providers: [AppService],
})
export class AppModule {}

Requirements

  • A version of Node with native fetch(); >=17.5 with fetch() flagged on, or >=18.0 which has fetch() enabled by default.
  • NestJS >= 8.x

License

This project is MIT licensed.