Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

If i used PassportStrategy as LocalStrategy, FacebookStrtegy....,
I can't use typesystem like autocomplete by ts in super();

export class LocalStrategy extends PassportStrategys(Strategy) {
  constructor(private authService: AuthService) {
    super(); // ts system not work!
  }
}

// in passport.strategy.d.ts
import { Type } from '../interfaces';
export declare function PassportStrategy<T extends Type<any> = any>(Strategy: T, name?: string | undefined): {
    new (...args: any[]): InstanceType<T>; // any is sad
};

Describe the solution you'd like

It can use typesystem!

export declare function PassportStrategy<T extends Type<any> = any>(
  Strategy: T,
  name?: string, // undefined type is unnecessary
): { new (...args: ConstructorParameters<T>): InstanceType<T> };
// ConstructorParameters<> is Typescript default UtilityType 

link: https://www.typescriptlang.org/docs/handbook/utility-types.html#constructorparameterstype

Teachability, documentation, adoption, migration strategy

we can just use same code but can use autocomplete, type check, prefix.......

What is the motivation / use case for changing the behavior?

1. I don't like "any type".
2. If i use Strategy, I have to check Strategy constructor parameter type in strategy.d.ts.
3. If i write wrong parameter, I can check immediately.