container.resolve type auto-inference feature about awilix HOT 1 CLOSED

What you are asking for specifically is not possible since it would require chaining all registrations in order to build the type map.

The next best thing is to define a modules collection type and use that in createContainer:

interface Modules {
  service: Service
}

const container = createContainer<Modules>()
container.register({
  // This should now be typed
  service: asClass(MyService)
})

// Returns expected type
container.resolve('service');

However, .resolve (and .cradle) are usually only used for entrypoints and for library integrations, 99% of your code using Awilix will be exclusively DI, and there is no way for Awilix to guarantee that constructor(service: Service) is upheld. However, in practice I have found that is rarely (if ever) an issue.

Awilix makes that trade-off in order to not invade your codebase; in other words, your application code should not be littered with Awilix imports.

from awilix.