Troubleshooting

Module not initialized

Make sure @quik/logging is registered in your bootstrap module. If it is not, getLogger() falls back to the framework's default IQLogger feature from @quik/core, which is not configured from logs.*.

No log output

Check logs.enabled — when false, the module installs QNoLogger regardless of logs.type. Also check logs.level: messages below the configured Winston level are silently discarded (e.g. debug calls do nothing when logs.level is info).

Unexpected logger type in CLI commands

When IQModuleSetup.isCli is true, setup() always builds a QConsoleLogger and ignores logs.type — this is intentional so CLI output stays human-readable even when the app config selects json.

logs.type value has no effect

getLoggerByType() only special-cases json (QJSONLogger) and no_logger (QNoLogger); every other value, including file and json_file from the QLoggerType enum, currently resolves to QConsoleLogger.

Common Errors

@quik/logging has no locales/ folder and defines no quik.errors.* keys of its own — logger construction does not raise typed errors; invalid logs.type/logs.level values silently fall back to console output/INFO level instead of throwing.