| name | teqfw-cfg |
| description | Use this skill when integrating, using, testing, reviewing, or modifying Node.js TeqFW applications that use @teqfw/cfg Sources, Loader, Store, Reader, raw configuration values, dotenv files, namespaces, or configuration lifecycle handling.
|
| license | Apache-2.0 |
| metadata | {"package":"@teqfw/cfg"} |
@teqfw/cfg
Use this skill for consumer code that composes or depends on the installed @teqfw/cfg package. Treat the host project's instructions, architecture, and test conventions as authoritative.
Apply
- Register the package through its
package.json#teqfw.fw.di.namespaces metadata, or add the TeqFw_Cfg_ namespace root in the Node.js composition root.
- Resolve cfg only through TeqFW DI CDC identifiers; the package has no root runtime import, export map, or supported
src/** deep import.
- Select Sources explicitly, call
Loader.load() once during bootstrap, and await it before resolving configuration-consuming runtime.
- Treat the Store snapshot as infrastructure-owned and immutable; use Reader only for fresh detached raw namespace fragments, then let each consumer parse, validate, and freeze its typed settings.
- Read the references selected below before editing, then validate with the host project tests.
Select References
| Consumer task | Read |
|---|
| Understand package boundary, ownership, namespaces, or composition | Concepts, Usage |
| Configure loading, precedence, lifecycle, or startup ordering | Lifecycle, Usage, Package API |
| Use or implement Object, process-environment, dotenv, or custom Sources | Sources, Values |
| Read raw values or build typed package settings | Values, Concepts |
| Handle or test cfg failures | Errors, Lifecycle, Package API |
| Discover the installed skill | Distribution |
cfg creates one immutable raw application snapshot from ordered Sources. It does not create typed application configuration, schemas, package discovery, configuration registration, or secret-management policy.
