Body

Summary

The ability for an integration to define middleware so that users do not need to go through the boilerplate of creating a middleware file and importing the functionality.

Background & Motivation

When we built the middleware API we anticipated a need for integrations to hook into it, but we decided not to make that a goal for v1 due to the complexity of ordering. Yet the need keeps coming up for the same reasons as before, integrations want to transparently add middleware.

Goals

• The ability to get middleware into an Astro project simply by adding an integration as normal.
• Allow an integration to place itself either at the front or end of the stack in terms of ordering.

Example

export default function() {
  return {
    name: 'astro-auth-middleware',
    hooks: {
      'astro:config:setup': ({ addMiddleware }) {
        addMiddleware({
          entrypoint: 'astro-auth-middleware/middleware',
          enforce: 'pre' // (or 'post')
        });
      }
    } 
  }
}