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

ee-webservice

v1.0.1

Published

webservice module supporting any «ee» middleware

Downloads

6

Readme

ee-webservice

Webservice implementation with support for middleware

build status

Build Status

Usage

Constructor

var Webservice = require('ee-webservice');

var service = new Webservice({
	  port: 		13023
	, interface: 	Webservice.IF_ANY
});

use method

Every middleware will be called with exactly 3 parameters:

  • request: request object of the ee-webserver

  • response: response object of the the ee-webserver

  • next: callback to be called for executing the next middleware

    // use a simple middleware for all hostnames not matched by a specific rule service.use(function(request, response, next){});

    // use a middleware which has a request method for all hostnames not matched by a specific rule service.use({request: function(request, response, next){}});

    // use a middleware for a single hostname service.use('joinbox.com', function(request, response, next){});

    // use a middleware for two absolute domain names and one with a wildcard subdomain service.use(['*joinbox.com', 'eventemitter.com', 'www.eventemitter.com'], function(request, response, next){});

    // use a middleware for all hostnames service.use('*', function(request, response, next){});

Interface Configurations

IF_PUBLIC: 1			// listen on all public interfaces
IF_PRIVATE: 2			// listen on all private interfaces ( RFC 1918, 192.168.x.y, 10.x.y.z, 172.16.x.y - 172.31.x.y, fc00:: )
IF_INTERNAL: 3 			// lis§ten on localhost ( 127.0.0.1, ::1, fe80::1 )
IF_LOCAL: 4 			// link local 169.254.1.x to 169.254.254.y, fe80::
IF_ANY: 5				// listen on any interface
IF_V4_PRIVATE: 10		// private v4 interfaces
IF_V6_PRIVATE: 20 		// private v6 interfaces
IF_V4_INTERNAL: 11 		// 127.0.0.1
IF_V6_INTERNAL: 21 		// fc00::
IF_V4_PUBLIC: 12
IF_V6_PUBLIC: 22
IF_V4_LOCAL: 13 		// §169.254.1.x to 169.254.254.y
IF_V6_LOCAL: 23 		// fe80::
IF_V4_ANY: 14
IF_V6_ANY: 24