Fix published provideClass return type inference.

[kburov-sc]

Without the type assertion, compiler resulting npm package type definition for provideClass looks like:

providesClass: <Token extends TokenType, Service, Tokens extends readonly ValidTokens<Services>[]>(token: Token, cls: InjectableClass<Services, Service, Tokens>) => Container<AddService<Services, Token, import("./Injectable").ConstructorReturnType<InjectableClass<Services, Service, Tokens>>>>;

The last bit (ConstructorReturnType<InjectableClass<Services, Service, Tokens>>>>) is somehow problematic. Resolving types for services provided using the function breaks, e.g. container.providesClass('serivice', Service) returns a container of type Container<{ service: any }>.

The fix addresses the issue by asserting the function's return type, so the generated function signature looks like:

providesClass: <Token extends TokenType, Service, Tokens extends readonly ValidTokens<Services>[]>(token: Token, cls: InjectableClass<Services, Service, Tokens>) => Container<AddService<Services, Token, Service>>;

With that container.providesClass('serivice', Service) correctly returns a container of type Container<{ service: Service }>.

[mikalai-snap]

I would prefer if we have return type explicitly declared on this method. There is a eslint rule for this, I'm thinking to enable it. That will not solve our problem, but that will prevent similar issues to happen in future when TS infers type incorrectly.

[kburov-sc]

Done! 93365db