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

ngnx-http

v0.0.20

Published

A simplified HTTP server.

Downloads

13

Readme

NGNX.http.Server

This is an NGN extension that simplifies common web serving. It's a slightly opinionated implementation of express that enforces good practices and simplifies development.

The following features are built in:

  1. Simple Routing
  2. Automatic Refresh
  3. CORS support
  4. TLS/SSL support
  5. Autostart

Usage

require('ngn')
require('ngnx-http')

let server = new NGNX.http.Server({
  poweredby: 'Acme Corp.'
})

server.createRoutes('./path/to/routes')

The code above will automatically start a web server on port 80 using the routes defined in /path/to/routes.js. That file may look like:

module.exports = function (app) {
  app.get('/echo', function (req, res) {
    res.status(200).send(req.body)
  })

  app.get('/ping', function (req, res) {
    res.sendStatus(200)
  })
}

We like to use a variation of this that relies on separating functionality into modules:

module.exports = function (app) {
  let auth = require('./tokenauth.js')
  let users = require('./my/users')

  app.post('/user', auth.required, users.create)
  app.get('/user/:id', auth.required, users.read)
  app.put('/user/:id', auth.required, users.update)
  app.delete('/user/:id', auth.required, users.delete)
  app.get('/users', users.list)
}

Automatic Refresh

By default, automatic refresh is enabled. It's better to turn this off in production (which can be done through an environment variable), but it can really speed up development.

The server.createRoutes() method is unique. It identifies files like the example above and adds the routes. It also monitors these files for changes and updates the server without restarting it (hot-route-loading). When a file is removed, it's routes are removed. When a file is modified, the routes are synchronized.

It's unlikely that a file will be deleted and recreated, but if it is, the routes will automatically be added when the file is re-added.