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

@networkoptix/request-interceptor

v0.1.1

Published

![Nx Meta Logo](https://meta.nxvms.com/static/images/logo.png)

Downloads

4

Readme

Nx Meta Logo

Request Interceptor License: MPL--2.0"

What is @networkoptix/request-intereptor?

This package allows intercepting request and applying middleware that can modify the request before it is handled by the browser/node or to modify a response before it's return back to the application.

What can it do?

The RequestInterceptor class handles handles registering middleware that intercepts requests and responses.

The middleware classes are all derived from the RequestMiddleware class. They can be configured to handle requests, responses, or both.

The middleware applied to the requests/reponses in the order that they are declared.


Usage

The RequestInterceptor class exposes a register static method which is used to initialize the interceptor. This method accepts an array of RequestMiddleware to apply to requests/responses.


Middleware

Included in the package are abstract and concrete classes for handling common use cases.

Generally concrete class names start with the word With to make it clear if it's an abstract or concrete class. So SomeMiddleware would be an abstract class and WithAnotherMiddleware would be a concrete class.

Abstract Middleware

An example abstract middleware class would be the AuthenticationMiddleware which defines shouldAuthenticate and authenticate classes and simplifies creating concrete middleware that handles various authentication schemes.

Concrete Middleware

An example abstract middleware class would be the WithBearerMiddleware which defines specific implementation of the shouldAuthenticate and authenticate methods to handle bearer token authentication.

Nx Meta Middleware

The Nx Meta middleware are specialized for interacting with Nx Meta services. These middleware classes will start with either Nx for abstract classes or WithNx for concrete classes.


Example of creating custom middleware from abstract class:

import { AuthenticationMiddleware } from '@networkoptix/request-interceptor'

export class WithBearerMiddleware extends AuthenticationMiddleware {
    async authenticate(request: Request): Promise<void> {
        request.headers.set('authorization', `Bearer ${await this.getToken()}`);
    }

    constructor(
        private getToken: (request?: Request) => string | Promise<string>,
        protected shouldAuthenticate: (request?: Request) => boolean
    ) {
        super();
    }
}

Example usage of concrete middleware:

The interceptor should be registered as early in the application lifecycle as possible.

For most applications it would be included in a main.ts or main.js file or a polyfills file.

import { WithBearerMiddleware, RequestInterceptor } from '@networkoptix/request-interceptor'

import { getToken, shouldAuthenticate } './from-other-module'

const middlewares = [
  new WithBearerMiddleware(getToken, shouldAuthenticate)
]

RequestInterceptor.register(middlewares)