In one of my middlewares I have a promise that needs to return before it can continue
however, if I add async/await to the function, I get a whole load of errors and pain
I’m returning a promise to a variable set in the middleware
I don't do any async/await in the middleware
but then I await it when I use it later on
HELP! Love Middy so far. Having an issue with writing jest tests with my custom middleware written with async/await. My middleware has a proper try/catch around the await. I've looked at the
ssm middleware that is part of the core for ideas. My middleware works fine when I remove that single async call to S3. But with it I keep getting UnhandledPromiseRejectionWarning
Is there some special way to implement a middleware that uses async/await
@lmammino Would love if you have a moment to chime in on this. middyjs/middy#270 Seems like a current limitation when trying to test custom middleware.
If anyone is in Calgary, be sure to hit me up.
Does anybody know how to assign error message for validation on input schema object?
Hey all! Is there any preferred way of reusing a configured set of middlewares?
I have a handler configured:
const handler = middy(async (event, context, callback) => {
(...)
callback(null, { });
});
handler.use(middleware1())
handler.use(middleware2())
handler.use(middleware3())
handler.use(middleware4())
module.exports = { handler };I'm looking for a good way of only having to specify something like:
const handler = withMiddlewares(async (event, context, callback) => {
(...)
callback(null, { });
});
module.exports = { handler };Where the handler is pre-configured with a bunch of middlewares.
I'm trying to avoid duplicating a bunch of handler configurations that are all going to be the same / similar.
Cheers!
Hi! I'm having some issues while working with
middy and httpErrorHandler middleware. I am using AWS Lambdas through an API Gateway, I have wrapped my handler in a middy() function and also applied the middlewares with .use(). When I need to throw an error inside my Lambda handler, I use the createError method from the http-errors library. But for some reason, the lambda response is always a 502 with {"message": "Internal server error"}. Am I missing something?
Hey there! Big fan of middy.js - it takes so much pain away. I was wondering if there's a standard approach to routing, i.e. one Lambda function that serves several of API endpoints with different handlers depending on the .routeKey (or .httpMethod + .resource)? Searching for router or routing on the issue tracker returns nothing.
hi everyone, I'm new to middy and I would like to create an official middleware for MikroORM (a typescript ORM I'm using). I'm using typescript on my project but I cannot find no typescript example on how to correctly use a middleware with typings and lambda or an example of custom middleware developed with typescript. Is there someone that has already did that and can share some example/process?
Happy New Year everyone! It's been a growing year for Middy with lots of adoptions (see below). Thank you for all of your help over the past year in making middy better than ever. We have some great news to start the year off with; I've started working on middy v2. We're addressing some of your most requested features and performance bottlenecks but will need to make some breaking changes. My goal is to have something together over the coming month so the community can comment. I'm hopeful AWS will support Node.js v14 around Apr/May and plan to have an alpha release ready for then.

Full trend details at middyjs/middy#590
1 reply