awilix-manager


Wrapper over awilix to support more complex use-cases

Getting started

First install the package:

``bash
npm i awilix-manager
`

Next, set up your DI configuration:

`js
import { AwilixManager } from 'awilix-manager'
import { asClass, createContainer } from 'awilix'

class AsyncClass {
async init() {
// init logic
}

async dispose() {
// dispose logic
}
}

const diContainer = createContainer({
injectionMode: 'PROXY',
})

diContainer.register(
'dependency1',
asClass(AsyncClass, {
lifetime: 'SINGLETON',
asyncInitPriority: 10, // lower value means its initted earlier
asyncDisposePriority: 10, // lower value means its disposed earlier
asyncInit: 'init',
asyncDispose: 'dispose',
eagerInject: true, // this will be constructed and cached immediately. Redundant for resolves with asyncInit parameter set, as that is always resolved eagerly. If a string is passed, then additional synchronous method will be invoked in addition to constructor on injection.
}),
)

const awilixManager = new AwilixManager({
diContainer,
asyncInit: true,
asyncDispose: true,
strictBooleanEnforced: true,
})
await awilixManager.executeInit() // this will execute eagerInject and asyncInit
await awilixManager.executeDispose() // this will execute asyncDispose
`

Disabling eager injection conditionally

In some cases you may want to prevent eager injection and async disposal of some of your dependencies - e. g. when you want to disable all of your background jobs or message consumers in some of your integration tests.
You can use enabled resolver parameter for that:

`js
import { AwilixManager } from 'awilix-manager'
import { asClass, createContainer } from 'awilix'

class QueueConsumerClass {
async consume() {
// consumer registration logic
}

async destroy() {
// dispose logic
}
}

const diContainer = createContainer({
injectionMode: 'PROXY',
})

const isAMQPEnabled = false // disable consumers, e. g. for tests

diContainer.register(
'dependency1',
asClass(QueueConsumerClass, {
lifetime: 'SINGLETON',
asyncInitPriority: 10, // lower value means its initted earlier
asyncDisposePriority: 10, // lower value means its disposed earlier
asyncInit: 'consume',
asyncDispose: 'destroy',
enabled: isAMQPEnabled, // default is true
}),
)

const awilixManager = new AwilixManager({
diContainer,
asyncInit: true,
asyncDispose: true,
strictBooleanEnforced: true,
})
await awilixManager.executeInit() // this will not execute asyncInit, because consumer is disabled
await awilixManager.executeDispose() // this will not execute asyncDispose, because consumer is disabled
`

Note that passing undefined or null as a value for the enabled parameter counts as a default, which is true. That may lead to hard-to-debug errors, as it may be erroneously assumed that passing falsy value should equal to passing false. In order to prevent this, it is recommended to set strictBooleanEnforced flag to true, which would throw an error if a non-boolean value is explicitly set to the enabled field. In future semver major release this will become a default behaviour.

Debug logging

You can enable debug logging to see when each dependency starts and finishes initializing during asyncInit. This is especially helpful when your application is timing out during the awilix init phase, as it allows you to identify which dependency is hanging or taking too long to initialize.

`js
import { AwilixManager } from 'awilix-manager'
import { asClass, createContainer } from 'awilix'

const diContainer = createContainer({
injectionMode: 'PROXY',
})

diContainer.register(
'dependency1',
asClass(MyClass, {
lifetime: 'SINGLETON',
asyncInit: true,
asyncInitPriority: 1,
}),
)

diContainer.register(
'dependency2',
asClass(AnotherClass, {
lifetime: 'SINGLETON',
asyncInit: true,
asyncInitPriority: 2,
}),
)

const awilixManager = new AwilixManager({
diContainer,
asyncInit: true,
enableDebugLogging: true, // enables debug logging
loggerFn: console.log, // optional, defaults to console.log
})

await awilixManager.executeInit()
// Logs:
// asyncInit: dependency1 - started
// asyncInit: dependency1 - finished
// asyncInit: dependency2 - started
// asyncInit: dependency2 - finished
`

You can also provide a custom logger function:

`js
const awilixManager = new AwilixManager({
diContainer,
asyncInit: true,
enableDebugLogging: true,
loggerFn: (message) => myLogger.debug(message),
})
`

Debug logging is also available when using the asyncInit function directly:

`js
import { asyncInit } from 'awilix-manager'

await asyncInit(diContainer, {
enableDebugLogging: true,
loggerFn: console.log,
})
`

Non-blocking async initialization

In some cases you may want to fire off an async initialization without waiting for it to complete. This is useful for background tasks that don't need to be ready before the application starts accepting requests.

You can use the object syntax for asyncInit with the nonBlocking option:

`js
import { AwilixManager } from 'awilix-manager'
import { asClass, createContainer } from 'awilix'

class BackgroundJobProcessor {
async asyncInit() {
// Start processing jobs in the background
// This may take a long time and we don't want to block startup
await this.connectToJobQueue()
await this.startProcessing()
}
}

class CriticalService {
async asyncInit() {
// This must complete before the app is ready
await this.loadConfiguration()
}
}

const diContainer = createContainer({
injectionMode: 'PROXY',
})

diContainer.register(
'criticalService',
asClass(CriticalService, {
lifetime: 'SINGLETON',
asyncInit: true, // blocking (default behavior)
asyncInitPriority: 1,
}),
)

diContainer.register(
'backgroundProcessor',
asClass(BackgroundJobProcessor, {
lifetime: 'SINGLETON',
asyncInit: { nonBlocking: true }, // fire-and-forget
asyncInitPriority: 2,
}),
)

const awilixManager = new AwilixManager({
diContainer,
asyncInit: true,
})

// This will:
// 1. Wait for criticalService.asyncInit() to complete
// 2. Start backgroundProcessor.asyncInit() but NOT wait for it
await awilixManager.executeInit()

// At this point, criticalService is ready, but backgroundProcessor may still be initializing
`

You can also specify a custom method name or function with the object syntax:

`js
// Using a custom method name
diContainer.register(
'consumer',
asClass(QueueConsumer, {
asyncInit: { method: 'startConsuming', nonBlocking: true },
}),
)

// Using a custom function
diContainer.register(
'processor',
asClass(Processor, {
asyncInit: {
method: (instance, diContainer) => instance.start(diContainer.cradle.config),
nonBlocking: true,
},
}),
)
`

Note that errors thrown during non-blocking initialization will not propagate to the caller. Method existence is validated synchronously before the async initialization starts, so missing methods will still throw errors immediately.

Fetching dependencies based on tags

In some cases you may want to get dependencies based on a supplied list of tags.
You can use tags parameter in conjunction with the getWithTags method for that:

`js
import { AwilixManager } from 'awilix-manager'
import { asClass, createContainer } from 'awilix'

const diContainer = createContainer({
injectionMode: 'PROXY',
})

class QueueConsumerHighPriorityClass {
}

class QueueConsumerLowPriorityClass {
}

diContainer.register(
'dependency1',
asClass(QueueConsumerHighPriorityClass, {
lifetime: 'SINGLETON',
asyncInit: true,
tags: ['queue', 'high-priority'],
}),
)
diContainer.register(
'dependency2',
asClass(QueueConsumerLowPriorityClass, {
lifetime: 'SINGLETON',
asyncInit: true,
tags: ['queue', 'low-priority'],
}),
)

const awilixManager = new AwilixManager({
diContainer,
asyncInit: true,
asyncDispose: true,
})

// This will return a record with dependency1 and dependency2
const result1 = awilixManager.getWithTags(['queue'])
// This will return a record with only dependency2
const result2 = awilixManager.getWithTags(['queue', 'low-priority'])
`

Fetching dependencies based on a predicate

In some cases you may want to get dependencies based on whether they satisfy some condition.
You can use getByPredicate method for that:

`js
import { AwilixManager } from 'awilix-manager'
import { asClass, createContainer } from 'awilix'

const diContainer = createContainer({
injectionMode: 'PROXY',
})

class QueueConsumerHighPriorityClass {
}

class QueueConsumerLowPriorityClass {
}

diContainer.register(
'dependency1',
asClass(QueueConsumerHighPriorityClass, {
lifetime: 'SINGLETON',
asyncInit: true,
}),
)
diContainer.register(
'dependency2',
asClass(QueueConsumerLowPriorityClass, {
lifetime: 'SINGLETON',
asyncInit: true,
}),
)

const awilixManager = new AwilixManager({
diContainer,
asyncInit: true,
asyncDispose: true,
})

// This will return a record with dependency1
const result1 = awilixManager.getByPredicate((entry) => entry instanceof QueueConsumerHighPriorityClass)
// This will return a record with dependency2
const result2 = awilixManager.getByPredicate((entry) => entry instanceof QueueConsumerLowPriorityClass))
`

Note that this will resolve all non-disabled dependencies within the container, even the ones without eager injection enabled.

Mocking dependencies

Sometimes you may want to intentionally inject objects that do not fully conform to the type definition of an original class. For that you can use asMockClass, asMockFunction or asMockValue resolvers:

`ts
type DiContainerType = {
realClass: RealClass
realClass2: RealClass
}
const diConfiguration: NameAndRegistrationPair = {
realClass: asClass(RealClass),
realClass2: asMockClass(FakeClass),
}

const diContainer = createContainer({
injectionMode: 'PROXY',
})

for (const [dependencyKey, dependencyValue] of Object.entries(diConfiguration)) {
diContainer.register(dependencyKey, dependencyValue as Resolver)
}

const { realClass, realClass2 } = diContainer.cradle
expect(realClass).toBeInstanceOf(RealClass)
expect(realClass2).toBeInstanceOf(FakeClass)
``