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-cli

v2.1.0

Published

Simple Node.js command-line HTTP server with CORS support.

Downloads

18

Readme

http-cli

Simple Node.js command-line HTTP server with CORS support.

It uses the following modules and middlewares :

For more details, see also Connect/Express middlewares.

Installation

npm install http-cli

Usage

Command line options are :

Options

  -h, --help            Display this usage help.
  -p, --port number     Listen port number.
  -a, --host string     Listen ip address or hostname.
  -r, --root string     Root folder path.
  -c, --config string   JSON configuration load file path.
  -d, --dump string     Default JSON configuration save file path.

Default behaviour is :

  • accept connections on 127.0.0.1 and port 8000
  • use combined log output
  • use current directory as web root
  • directory listing is enabled
  • send "index.html" files in response to a request on a directory
  • reflect the request origin header in Access-Control-Allow-Origin CORS header

Configuration

An optionnal JSON configuration file can be loaded with --config option.

Example configuration file :

{
  "port": 3000,
  "host": "0.0.0.0",
  "root": "./web/",
  "middlewares": [
    {
      "name": "cors",
      "cfg": {
        "origin": "http://example.com"
      }
    },
    {
      "name": "serveStatic",
      "cfg": {
        "index": ["index.html", "default.html"]
      }
    },
    {
      "name": "serveIndex",
      "cfg": {
        "view": "details"
      }
    }
  ]
}

For middlewares options, see links above.

Default configuration is equivalent to :

{
  "port": 8000,
  "host": "127.0.0.1",
  "root": "./",
  "logFormat": "combined",
  "middlewares": [
    {
      "name": "cors",
      "cfg": {
        "origin": true
      }
    },
    {
      "name": "morgan",
      "cfg": {}
    },
    {
      "name": "serveStatic",
      "cfg": {}
    },
    {
      "name": "serveIndex",
      "cfg": {
        "icons": true
      }
    }
  ]
}

The default configuration can be saved to file with --dump option.

Node.js module

const http = require('http-cli')

const config = new http.Config()
// config.loadFromFile('path/to/config.json')
// config.port(8090)

http.server(config)
  .listen(config.port(), config.host(), function() {
    console.log('http server listening on ' + config.host() + ':' + config.port())
  })

Middlewares are "used" in the same order as the configuration array.

Some configuration helpers are available to facilitate the addition of middleware.

const http = require('http-cli')

const config = new http.Config()

config.use(function(req, res, next) {
  // this middleware is used at the end
  next()
})

config.useBefore('serveIndex', function(req, res, next) {
  // this middleware is used before serveIndex middleware
  next()
})

config.useAfter('cors', function(req, res, next) {
  // this middleware is used after cors middleware
  next()
})

http.server(config)
  .listen(config.port(), config.host(), function() {
    console.log('http server listening on ' + config.host() + ':' + config.port())
  })

License

MIT