Type issue with supertest and `app.getHttpServer()` about nest

[coler-j]

Can get around this by doing NestExpressApplication instead of INestAppliction or INestApplication<NestExpressApplication>

[micalevisk]

so the "issue" is because app.getHttpServer() has any as the return type, right?

I guess that's because of the following change: cf4097c

now INestApplication has a type arg, which defaults to any

nest/packages/common/interfaces/nest-application.interface.ts

Line 24 in 8cfa854

export interface INestApplication<TServer = any>

I'm not sure if we can improve that or if you just need to type that INestApplication better

[coler-j]

Well, how would I type the INestApplication better than doing INestApplication<NestExpressApplication>? I don't think there is anything else that would make sense in the context that it is being used.

i.e. the error occurs still with INestApplication<NestExpressApplication>

Edit:

Actually, a different error is encountered

[micalevisk]

It should be: INestApplication<Server> where Server is from net (nodejs module)

Still, I'm not sure if we can improve the typings of createNestApplication but I'd suggest you to try to improve it.

So this is not a bug but a feature request

[kamilmysliwiec]

Just pass <Server> as a type argument, as @micalevisk suggested above

When it comes to your ESLint rule, this isn't a bug (more explanation here nestjs/schematics#1700 (comment))

One thing we could improve is to mention this in the docs (if you have X rule enabled, then make sure to pass Server as a type argument).