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

surls

v0.0.1

Published

A connect middleware to ensure requests are switched between HTTP and HTTPS properly

Readme

surls

surls is a connect middleware to ensure requests are switched between HTTP and HTTPS based on a config.

Installation

npm

npm install surls

GitHub

npm install https://github.com/martinrue/surls/tarball/master

Configuration

The first thing you must do is call configure to specify which URLs should be secured. You can optionally specify the HTTP and HTTPS port numbers to use.

var surls = require('surls');

surls.configure(['/login', '/resetpassword'], { httpPort: 1234, httpsPort: 12345 });

URLs

URLs that are to be forced to HTTPS should be specified in the array passed to configure. You can specify an exact URL match using a string or provide a regex that will be tested against the current request URL. You can also use an asterisk to indicate that all URLs should be forced to HTTPS.

Examples

Only requests to /login and /account will be forced to HTTPS, all other requests will be forced to HTTP.

surls.configure(['/login', '/account']);

Requests to /secure0, /secure1, ... /secure9 will be forced to HTTPS, all other requests will be forced to HTTP.

surls.configure([/secure[0-9]/]);

All requests will be forced to HTTPS.

surls.configure(['*']);

Example Application

var fs = require('fs');
var http = require('http');
var https = require('https');
var express = require('express');
var surls = require('surls');

var options = {
  key: fs.readFileSync('server.key'),
  cert: fs.readFileSync('server.crt')
};

surls.configure([/secure[0-9]/], { httpPort: 1234, httpsPort: 12345 });

var app = express();

app.configure(function() {
  app.use(surls.secureUrls);
});

app.get('/', function(req, res) {
  res.send('index');
});

app.get('/secure1', function(req, res) {
  res.send('secure 1');
});

app.get('/secure2', function(req, res) {
  res.send('secure 2');
});

app.get('/secure3', function(req, res) {
  res.send('secure 3');
});

app.get('/securez', function(req, res) {
  res.send('secure Z');
});

http.createServer(app).listen(1234);
https.createServer(options, app).listen(12345);