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

kronos-interceptor

v2.6.0

Published

introspects / modifies requests as they pass between endpoints

Downloads

112

Readme

npm Greenkeeper semantic-release styled with prettier Build Status codecov.io Coverage Status Known Vulnerabilities GitHub Issues Stories in Ready Dependency Status devDependency Status docs XO code style downloads Commitizen friendly

kronos-interceptor

introspects / modifies requests as they pass between endpoints

const ki = require('kronos-interceptor');

const endpoint = { get name() { return 'aName'; }, receive() {}};
const interceptor1 = new ki.Interceptor({},endpoint);
const interceptor2 = new ki.Interceptor({},endpoint);

interceptor1.connected = interceptor2

const request = {};
const promise = interceptor1.receive(request);

API

Table of Contents

rejectingReceiver

rejecting receiver used to signal a not present connection when used always delivers a rejecting promise

Parameters

  • request

Returns Promise<Error>

ConnectorMixin

Mixin to make endpoints/interceptors connectable Forms a single linked list

Parameters

  • superclass

Interceptor

Extends ConnectorMixin(class {})

Base interceptor. The base class for all the interceptors Calls configure() and reset().

Parameters

  • config Object The interceptor configuration object.
  • endpoint Object the endpoint object this interceptor will be attached to.

logger

use endpoint owner as logger

type

The instance method returning the type. Defaults to the constructors name (class name)

Returns string

configurationAttributes

Meta description of the configuration

Returns Object

configure

Takes attribute values from config parameters and copies them over to the object. Copying is done according to configurationAttributes Which means we loop over all configuration attributes and then for each attribute decide if we use the default, call a setter function or simply assign the attribute value

Parameters

toJSON

Deliver the json representation

Returns Object json representation

reset

forget all accumulated information

receive

The receive method. This method receives the request from the leading interceptor and calls the trailing interceptor

Parameters

  • request Object the request from the leading interceptor
  • oldRequest Object the oldRequest from the leading interceptor. This is a special case. As some interceptors are in charge of copying and creating the request objects, the step will call the interceptor chain with the both requests. At some point of the interceptor chain only the request itself will survive. But all interceptors designed to be inserted early in the interceptor chain of a sending endpoint should pass both requests to the next interceptor.

Returns Promise

configurationAttributes

Meta description of the configuration

Returns Object

TimeoutInterceptor

Extends Interceptor

Rejects a request if it does not resolve in a given time

name

Returns string 'timeout'

rejectUnlessResolvedWithin

Parameters

Returns Promise

StatsCollectorInterceptor

Extends Interceptor

Interceptor to collect processing time, number of processed and failed requests

receive

Logs the time the requests takes

Parameters

  • request
  • oldRequest

name

Returns string 'collect-request-stats'

LimitingInterceptor

Extends Interceptor

Limits the number of concurrent requests. Requests can be delayed or rejected. Sample config: [ { count: 20 }, { count: 10, delay: 100 }, { count: 5, delay: 10 } ] 1 - 4 : no delay 5 - 9 : 10ms delay 10 - 19 : 100ms delay 20 : reject default is to reject when more than 10 requests are on the way

Parameters

  • config
  • endpoint

name

Returns string 'request-limit'

install

With npm do:

npm install kronos-interceptor

license

BSD-2-Clause