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

http-autodetect

v0.0.2

Published

Support deployment via FastCGI, Passenger, or node http.

Downloads

3

Readme

This is being renamed to autoserve.

Enable a webapp to get the optimal http implementation based on how it is deployed. Also provide a way to get the baseUrl of the deployment.

Ways one might deploy a node-based webapp:

  • http
  • node-fastcgi
  • CGI (in the future just as proof of concept, please don’t use in production)
  • Passenger

Usage

script.cgi:

#!/usr/bin/env node
'use strict';

const httpAutodetect = require('http-autodetect');

const app = function (req, res) {
    res.writeHead(200, { 'Content-Type': 'text/plain; charset=utf-8', });
    // It is recommended to use a framework like express to calculate
    // the host and protocol of your deployment. getBaseUrl() only
    // solves the path portion of the deployment.
    res.end(`Hello, World! I am deployed at https://${req.headers.host}${httpAutodetect.getBaseUrl(req)}`);
};

httpAutodetect(app);

Express Usage

You need extra middleware to get Express to respect getBaseUrl(). See express-http-autodetect for that or use this snippet:

#!/usr/bin/env node
'use strict';
const expressHttpAutodetect = require('express-http-autodetect');

// If you followed the Express-4 migration guide or used
// express-generator, your app definition will be its own
// CommonJS module.
const app = require('./app');

expressHttpAutodetect(app);

Note the Connect is not supported as it does not have the concept of managing baseUrl/mounting sub-apps. It only chains handlers and is missing the sort of routing handling that proper baseUrl handling requires.