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

@webtask/middleware-compiler

v1.5.2

Published

Webtask compiler that provides a configurable middleware pipeline

Downloads

58

Readme

Middleware compiler

The middleware compiler provides a mechanism to run any number of middleware prior to invoking a webtask.

Webtask middleware are disigned in a connect-compatible way that should allow many express middleware to just work.

Usage:

  1. Set the wt-node-dependencies metadata property to the stringified JSON of an object having a @webtask/middleware-compiler property whose value is the latest version of this module.

    {"@webtask/middleware-compiler":"1.1.0"}
  2. Set the wt-compiler metadata property on your webtask to @webtask/middleware-compiler.

  3. Optionally, set the wt-middleware metadata property to a comma-separated list of middleware references. Middleware references can be any combination of:

    • module_name - The name of an npm module, in which case the module's default export is used. This would be equivalent to require('module_name').
    • module_name/name_of_export_function - The name of an npm module with the name of the desired export. This wouldbe equivalent to require('module_name').name_of_export_function.
    • http(s)://url.of/a/file/exporting/a/middleware.js - A publicly accessible url from which the middleware's code will be downloaded and evaluated. The code must export a suitable middleware factory function as the default export.
  4. Optionally, set the wt-debug metadata property to a comma-separated list of debug references that contains wt-middleware. This will result in additional debug information being sent to real-time logs.

How it works

A middleware is a Function exported by a node module that returns another Function having the signature function(req, res, next), where:

  • req is the instance of http.IncomingRequest for the current request. It has a req.webtaskContext property:

  • res is the instance of http.ServerResponse for the current request

  • next is a function with the signature function next(error). A middleware function may be designed to complete the response, in which case it can omit calling next. A middleware may also implement authentication logic, such as the authentication middleware. In this case, the middleware might invoke next with an Error. If the error has a statusCode property, this will be used as the response status code. Otherwise, to allow control to go to the next middleware, or to the default middleware (which compiles and invokes the webtask code), the middleware can call next() with no arguments.

Example middleware

** Authentication **