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

aldo

v1.0.0-alpha.0

Published

Fast micro framework for Node.js 8+

Downloads

10

Readme

Aldo-application is an object containing a stack of middleware functions which are composed and executed upon each HTTP request.

const { Application } = require('aldo')

const app = new Application()

// add a request handler
app.use(() => 'Hello world!')

// create a HTTP server to serve the application
app.start(process.env.PORT)

Middlewares

Middlewares could be a common or an async function. Each function receives a request context and a next function to call the downstream middlewares, and must return a response as output.

// Handler function signature
declare type Middleware = (ctx: Context, next: () => any) => any;

You can register as many middlewares as needed with the application's method .use(fn)

// to add a handler directly in the stack
app.use(middleware)

Whether a middleware runs before or after a downstream middlewares depends on the middleware itself. For example, the following middleware would perform some task before the others

app.use((ctx, next) => {
  // Perform task

  return next()
})

However, this middleware would perform its task after the request is handled by the following middlewares

app.use(async (ctx, next) => {
  let response = await next()

  // Perform task

  return response
})

Context

The context object is a simple plain object with these properties:

  • request refers to the incoming request object
  • response function to get a new Response instance each time called
  • Other fields defined with .set(key, value) or .bind(key, getter)
declare interface Context {
  request: Request;
  response: ResponseFactory;
  [key: string]: any;
}

To extend the request context, and add shared properties, like a DB connection or a global logger, you may use .set(key, value)

const mongoose = require('mongoose')

await mongoose.connect('mongodb://localhost/test')

app.set('db', mongoose)

To set a per request private properties, you may use .bind(key, getter). This method takes a field name, and a function to be used as a lazy getter of the field value.

app.bind('session', () => new Session(options))

This method is very useful, since it allows you to lazily (only when needed) attach a per request property into the context without adding a dedicated handler.

.has(key) and .get(key) are aldo available to check the existence of a certain field or to get a previously defined field value.

Response

The middleware output could be:

  • strings or buffers sent directly
  • streams which will be piped to the outgoing response
  • null or undefind as empty responses (By default with 204 status code)
  • Response instances which can be created with the context response property
  • otherwise, any other value will be serialized as JSON, with the proper Content-Type and Content-Length