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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@kgryte/https-server

v1.0.3

Published

HTTPS server.

Downloads

24

Readme

HTTPS Server

NPM version Build Status Coverage Status Dependencies

HTTPS server.

Installation

$ npm install @kgryte/https-server

Usage

var httpsServer = require( '@kgryte/https-server' );

httpsServer( options, logger[, requestListener ] )

Returns a function to create an HTTPS server.

var bunyan = require( 'bunyan' );

// Specify server options...
var opts = {
	'key': 'path/to/private/key',
	'cert': 'path/to/public/certificate',
	'port': 7331,
	'address': '127.0.0.1'
};

// Create a logger...
var logger = bunyan.createLogger({
	'name': 'logger',
	'streams': [
		{
			'name': 'main',
			'level': 'info',
			'stream': process.stdout
		}
	]
});

// Create a function for creating an HTTPS server...
var create = httpsServer( opts, logger );

To bind a request callback to a server, specify a requestListener. For example,

var express = require( 'express' );

// Create a new application:
var app = express();

// Use the application as a request listener...
var create = httpsServer( opts, logger, app );

The function accepts the following options (along with any other tls.createServer options):

  • key: path to private key for TLS/SSL.
  • cert: path to public certificate for TLS/SSL.
  • port: server port. Default: 0 (i.e., randomly assigned).
  • maxport: max server port when port hunting. Default: maxport=port.
  • hostname: server hostname.
  • address: server address. Default: 0.0.0.0.

To specify a range of permissible ports, set the maxport option.

opts.maxport = 9999;

var create = httpsServer( opts, logger, app );

When provided a maxport option, a created server will search for the first available port on which to listen, starting from port.

create( done )

Creates an HTTPS server.

function done( error, server ) {
	if ( error ) {
		throw error;
	}
	console.log( 'Success!' );
	server.close();
}

create( done );

Notes

  • Port hunting can be useful in a microservice deployment. When a port is randomly assigned (options.port=0), if a server fails and is restarted, the server is unlikely to bind to its previous port. By allowing a constrained search, assuming no lower ports within a specified range have freed up in the meantime, the likelihood of listening on the same port is increased. A server can typically restart and bind to the same port faster than binding to a new port and re-registering with a microservice registry, thus minimizing possible service interruption and downtime.

Examples

var bunyan = require( 'bunyan' ),
	express = require( 'express' ),
	httpsServer = require( './../lib' );

// Specify server options...
var opts = {
	'key':'path/to/private/key',
	'cert': 'path/to/public/certificate',
	'port': 7331,
	'maxport': 9999,
	'hostname': 'localhost'
};

// Create a logger...
var logger = bunyan.createLogger({
	'name': 'logger',
	'streams': [
		{
			'name': 'main',
			'level': 'info',
			'stream': process.stdout
		}
	]
});

// Create an express app:
var app = express();

// Create a function for creating an HTTPS server...
var create = httpsServer( opts, logger, app );

/**
* FUNCTION: done( error, server )
*	Callback invoked once a server is ready to receive HTTP requests.
*
* @param {Error|Null} error - error object
* @param {Server} server - server instance
* @returns {Void}
*/
function done( error, server ) {
	if ( error ) {
		throw error;
	}
	console.log( 'Success!' );
	server.close();
}

// Create a server:
create( done );

To run the example code from the top-level application directory,

$ node ./examples/index.js

Tests

Unit

Unit tests use the Mocha test framework with Chai assertions. To run the tests, execute the following command in the top-level application directory:

$ make test

All new feature development should have corresponding unit tests to validate correct functionality.

Test Coverage

This repository uses Istanbul as its code coverage tool. To generate a test coverage report, execute the following command in the top-level application directory:

$ make test-cov

Istanbul creates a ./reports/coverage directory. To access an HTML version of the report,

$ make view-cov

License

MIT license.

Copyright

Copyright © 2015. Athan Reines.