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

nest-http-proxy

v0.1.1

Published

A Nest module wrapper for http-proxy-middleware

Downloads

15

Readme

nest-http-proxy

NPM version

A Nest module wrapper for http-proxy-middleware

Installation

To begin using it, we first install the required dependencies.

$ npm install --save nest-http-proxy http-proxy-middleware

Getting started

Once the installation is complete, import the HttpProxyModule into the root AppModule and run the forRoot() static method as shown below:

import { Module } from '@nestjs/common';
import { HttpProxyModule } from 'nest-http-proxy';

@Module({
  imports: [
    HttpProxyModule.forRoot({
      '/api': {
        target: 'http://www.example.org/api',
        changeOrigin: true,
      },
    }),
  ],
})
export class AppModule {}

The forRoot() method accepts a proxy table object to create and configure proxy middlewares.

Async configuration

When you need to pass module options asynchronously instead of statically, use the forRootAsync() method. As with most dynamic modules, Nest provides several techniques to deal with async configuration.

One technique is to use a factory function:

HttpProxyModule.forRootAsync({
  useFactory: () => ({
    '/api': {
      target: 'http://www.example.org/api',
      changeOrigin: true,
    },
  }),
});

Like other factory providers, our factory function can be async and can inject dependencies through inject.

HttpProxyModule.forRootAsync({
  imports: [ConfigModule],
  useFactory: async (configService: ConfigService) => 
    configService.get('proxyTable'),
  inject: [ConfigService],
});

Alternatively, you can configure the HttpProxyModule using a class instead of a factory, as shown below.

HttpProxyModule.forRootAsync({
  useClass: HttpProxyConfigService,
});

The construction above instantiates HttpProxyConfigService inside HttpProxyModule, using it to create an options object. Note that in this example, the HttpProxyConfigService has to implement HttpProxyModuleOptionsFactory interface as shown below. The HttpProxyModule will call the createHttpProxyOptions() method on the instantiated object of the supplied class.

@Injectable()
class HttpProxyConfigService implements HttpProxyModuleOptionsFactory {
  createHttpProxyOptions(): HttpProxyModuleOptions {
    return {
      '/api': {
        target: 'http://www.example.org/api',
        changeOrigin: true,
      },
    }
  }
}

If you want to reuse an existing options provider instead of creating a private copy inside the HttpProxyModule, use the useExisting syntax.

HttpProxyModule.forRootAsync({
  imports: [ConfigModule],
  useExisting: HttpProxyConfigService,
});

License

MIT