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

hyperbole

v1.0.1

Published

A promise based wrapper around http/https

Downloads

4

Readme

hyperbole

NPM version Dependency Status Dev Dependency Status Code Climate Build Status Coverage Status

Hyperbole is a Promise wrapper around the core node http and https modules.

Installation

npm install --save hyperbole

Usage

With express or other connect-like server handlers

var express = require('express');
var app     = require('app');
var server  = require('hyperbole')(app, 3000);

app.use(function (req, res) {
  res.json({hello: 'world'});
});

server.start()
  .then(function () {
    console.log('Server started on port %s', server.port);
  })
  .catch(function (err) {
    console.log(err);
  });

To make it an https server, pass in the required options as the third parameter.

var fs      = require('fs');
var express = require('express');
var app     = require('app');
var server  = require('hyperbole')(app, 443, {
  key: fs.readFileSync('key.pem'),
  cert: fs.readFileSync('cert.pem')
});

app.use(function (req, res) {
  res.json({hello: 'world'});
});

server.start()
  .then(function () {
    console.log('HTTPS server started on port %s', server.port);
  })
  .catch(function (err) {
    console.log(err);
  });

You can also have multiple servers.

var fs = require('fs');
var express = require('express');
var createServer = require('hyperbole');
var app = require('app');
var httpServer = createServer(app, 80);
var httpsServer = createServer(app, 443, {
  key: fs.readFileSync('key.pem'),
  cert: fs.readFileSync('cert.pem')
});

// Only redirect the root
app.get('/', function (req, res, next) {
  if (!req.secure) {
    return res.redirect('https://' + req.headers.host + req.url);
  }
  next();
});

// Send 426 "Upgrade Required" error to notify the user that they need to use
// https
app.use(function (req, res, next) {
  if (!req.secure) {
    return res.status(426).send('Switch to using https');
  }
  next();
});

app.use(function (req, res) {
  res.json({secure: true});
});

httpsServer.start()
  .then(httpServer.start)
  .then(function () {
    console.log('Both servers started');
  })
  .catch(function (err) {
    console.log(err);
  });

API

The exported object is actually a class-like object, so technically, it's probably better to do:

var Server = require('hyperbole');
var server = new Server(app, port);

but for convenience, you can just use it as a function, and it will return the new server instance.

It takes 3 arguments:

  • app (Function) - The handler that takes in the request and response objects to process each request. This is usually an express, koa, or connect app.
  • port (Number/String) - The port to bind to.
  • secure (Object) optional - If you want the server to be an https server, then pass in the options object as described here.

It returns a server instance.

Each instance has the following methods:

  • server.start()

    Starts the server. Returns a promise with no arguments passed.

  • server.stop()

    Stops the server. The server must have successfully started in order to stop it.

You can also access the http server object directly with server.server in case you were using it for socket.io or something else.