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

pro-xy

v0.1.18

Published

Pluggable node proxy

Downloads

51

Readme

pro-xy

Simple pluggable http proxy, which allows to define plugins, that can change request or response.

Usage

  1. Install

     npm install -g pro-xy
  2. Run.

     pro-xy

Alternatively pro-xy can also be required from another module and launched be calling start method.

Config file

Sample:

{
	"port": 8000,
	"logLevel": "DEBUG",
	"plugins": [
		"pro-xy-url-replace",
		"pro-xy-header-replace",
		"pro-xy-cookie-replace",
		"pro-xy-auto-responder"
	],
	"pro-xy-url-replace": {
		"disabled": false,
		"replaces": [],
		"replaceBackHeaders": [
			"location",
			"link"
		]
	},
	"pro-xy-auto-responder": {
		"disabled": true,
		"responses": []
	},
	"pro-xy-cookie-replace" : {
		"disabled": true,
		"replaces": []
	},
	"pro-xy-header-replace":{
		"disabled": true,
		"replaces": []
	}
}

This sample file defines port to start on, logging configuration and 4 plugins and their configuration.

  • port - port for proxy
  • plugins - list of plugins to use. Plugins are represented by name of their npm package and must be installed alongside pro-xy module

Plugins

Plugins are npm modules which export function that will be called for each request and will receive config, request and response. If function truthy value, it means it has processed the request completely and no following plugins and replaces will be applied.

module.exports = function(config, req, res) {
	//do something
	return false;
};

Instead of function plugin may export object with two methods init and exec, where exec should be same function as defined above and exec should be a function which will be called on pro-xy startup and will receive pro-xy instance an log4js logger instance for this pluggin,

var logger;
module.exports = {
	init: function (_proxy, _logger) {
		logger = _logger;
	},
	exec: function(config, req, res) {
		//do something
		//logger.trace(...)
		return false;
	}
};

Known plugins

User interface

See pro-xy-ui