core icon indicating copy to clipboard operation
core copied to clipboard

Application wiring, configuration, and boilerplate utilities

Results 33 core issues
Sort by recently updated
recently updated
newest added

**Bug description** During the init process, if something goes wrong in setting up a schedule then the entire app can crash without anything in particular being logged **How to reproduce**...

bug

Accept custom formatting, and provide examples for how to go to pino for json logging in docs

documentation
enhancement

Add the ability to generate a "defaults" configuration file via `boilerplate.BUILD_DEFAULT_CONFIG`. This will build a valid configuration file with all configuration properties in it. The value for everything should be...

enhancement
feat: configuration

Passing the `--help` flag should cause the application to print a document to the console describing the way the configuration system was wired together. This work **MUST** be done prior...

enhancement
feat: configuration

Currently, the `internal.config.onUpdate` only triggers for `.set` calls. This should be improved to also fire events as part of the bootstrap sequence - construct - preInit - configure - ***...

enhancement

#17 add the ability, on a per config item basis, to provide a desired config source for a configuration. environment (cli switch + env variables) are always available, file loading...

enhancement

## Issue It's not uncommon to want to gather some details about a parent service, normally this is handled by passing around a `context` variable. The `logger`, and `scheduler` have...

enhancement

## 🐜 Bug description Setting `bootLibrariesFirst` will cause app configs to not load at the same time as all the other configs, the registration appears to be happening too late...

bug

## 🐜 Bug description Core doesn't support ESM properly, and it's an issue that affects the larger code base. Something about the process is completely breaking tests in this code,...

bug

**Bug description** given the following code: ``` lifecycle.onPreShutdown(async () => { console.log('before await') await new Promise((resolve) => setTimeout(resolve, 1000)) console.log('after await') }) ``` The second console.log will not print during...

bug