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

express-autoserve

v0.0.2

Published

Automatically support different Express app deployment strategies such as FastCGI, Passenger, and node http.

Downloads

4

Readme

This module is being renamed to express-autoserve.

Autodetect the service platform and delegate to an Express app.

Usage

const expressAutoserve = require('express-autoserve');
const app = require('./app');

expressAutoserve(app);

Mechanics

req.baseUrl

The node http module has no concept of baseUrl because it assumes it will get to open the TCP socket itself and just serve out pages at /. However, various deployment strategies supported by autoserve are commonly used to deploy applications at URIs other than /. Thus autoserve provides a getBaseUrl(req) function to discover the baseUrl for the current request (in FastCGI, the necessary information is not available until a request is received).

Express supports mounting applications at sub-paths. To enable mounted applications to generate absolute URIs to resources within the apps, it provide the req.baseUrl property. This enables the following to work sensibly:

const express = require('express');

const app = express();

const subApp = express();
subApp.get('/asdf', function (req, res) {
   // When mounted, will get /subApp/foo
  res.send(`Another resource on this app is ${req.baseUrl}/foo`);
});
subApp.get('/foo', function (req, res) {
  res.send(`You found me!`);
});

app.use('/subApp', subApp);
app.listen(3000);

This module ensures that the passed app is treated like it is mounted in an express app at the baseUrl calculated by autoserve. This causes the baseUrl to be set properly for the passed app and ensures that routing is performed relative to the deployment baseUrl.