Express middleware `express-error-slack` doesn't work with NestJS, but works for express server

Bug Report

Current behavior

NestJS documentation explains that nest Middleware is the same as express middleware. However, when trying to use the express-error-slack middleware, it seems the function never gets called. This doesn’t seem to be a problem with the package itself, since the same package works as expected in express

https://github.com/chunkai1312/express-error-slack

Input Code

main.ts:

import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
import { ValidationPipe } from '@nestjs/common';
import * as helmet from 'helmet';
import * as expressslack from 'express-error-slack';

async function bootstrap() {
    const app = await NestFactory.create(AppModule);
    app.useGlobalPipes(new ValidationPipe());
    app.use(expressslack({ webhookUri: 'webhookURL' }));
    app.use(helmet());
    await app.listen(3000);
}
bootstrap();

Controller

@Controller()
export class MyController {
    @Get('error')
    async error() {
        throw new Error('Error!');
    }
}

I would expect the express slack middleware to pick up the error and handle it, but it’s not

Environment

Nest version: 6

For Tooling issues:

• Node version: 10.15.1
• Platform: Windows 10

[blitzmann]

@kamilmysliwiec I did not! Well I feel silly now. I will take ma look and verify this is what we’re looking for.

I also found a way to potentially do it with interceptors, was about to edit my response above with that information.

I still feel like the documentation should explicitly mention the issues with express error handling middleware. I assume there’s quite a few packages out there that wouldn’t work because of that. Unless I missed that in the documentation as well >.<

[kamilmysliwiec]

It’s actually a duplicate of this https://github.com/nestjs/docs.nestjs.com/issues/215