Would it be possible to use async-middleware-wrap as TS decorator ? Something like:

@Wrap
public async apiHandler (req:Request, res:Response) {

Version 8.0.44 of @types/node was just published.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 8.0.18 of @types/node just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 2.0.8 of typescript just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As typescript is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

With the latest version of @types/express, I cannot use wrap() without having to explicitly declare the types of req, res and next.

Without wrap(), the types are inferred.

This is especially unfortunate because app.get() is now generic and you customize the parameter types of a route, but this way you need to duplicate them.

G'day, it looks like Express has updated their type definition of NextFunction to:

export interface NextFunction {
    (err?: any): void;
    /**
     * "Break-out" of a router by calling {next('router')};
     * @see {https://expressjs.com/en/guide/using-middleware.html#middleware.router}
     */
    (deferToNext: "router"): void;
}

Which means it is incompatible with the NextFunction definition in this module's index.d.ts.

I'm working around this myself by explicitly importing NextFunction from Express to type the wrapper function.

Cheers!

Version 2.4.1 of typescript just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As typescript is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴