npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@nl-framework/config

v0.3.5

Published

Configuration module for nl-framework with DI integration and YAML loading utilities.

Readme

@nl-framework/config

Configuration utilities for the NL Framework. This package wraps the core ConfigLoader and ConfigService with a module-first API so you can expose configuration values through dependency injection.

Installation

bun add @nl-framework/config

Quick start

Register the module at the root of your application. By default it loads YAML files from the config directory (default.yaml, <env>.yaml, then env.yaml):

import { Module } from '@nl-framework/core';
import { ConfigModule, ConfigService } from '@nl-framework/config';

@Module({
  imports: [
    ConfigModule.forRoot({
      dir: 'config',
      path: 'env.yaml',
      overrides: {
        app: { port: 4000 },
      },
    }),
  ],
})
export class AppModule {
  constructor(private readonly config: ConfigService) {}
}

Resolve values anywhere in your DI graph:

@Injectable()
export class AppService {
  constructor(private readonly config: ConfigService) {}

  getPort(): number {
    return this.config.get<number>('app.port', 3000);
  }
}

Async options

Use forRootAsync when configuration comes from other providers:

@Module({
  imports: [
    ConfigModule.forRootAsync({
      useFactory: async () => ({
        dir: 'config',
        overrides: {
          feature: {
            cache: process.env.ENABLE_CACHE === 'true',
          },
        },
      }),
    }),
  ],
})
export class AppModule {}

You can also provide a class that implements ConfigModuleOptionsFactory.

Feature slices

Expose nested configuration once and inject it elsewhere using forFeature:

import { Inject } from '@nl-framework/core';
import { ConfigModule, getConfigFeatureToken } from '@nl-framework/config';

const databaseConfigToken = getConfigFeatureToken('database');

@Module({
  imports: [
    ConfigModule.forRoot(),
    ConfigModule.forFeature('database'),
  ],
})
export class DatabaseModule {
  constructor(@Inject(databaseConfigToken) private readonly config: Record<string, unknown>) {}
}

The token is stable (Symbol.for('nl:config:feature:<path>')) so you can reuse it without storing a reference.

API

  • ConfigModule.forRoot(options?: ConfigModuleOptions) — Load YAML configuration using explicit options.
  • ConfigModule.forRootAsync(options: ConfigModuleAsyncOptions) — Resolve options via DI (useFactory, useClass, or useExisting).
  • ConfigModule.forFeature(pathOrOptions) — Provide a specific config slice (with optional transform) as an injectable token.
  • ConfigService — Re-exported from @nl-framework/core for convenience.
  • ConfigLoader — Re-exported loader utility for manual use.

Testing

This package ships with Bun tests. Run them with:

bun run packages/config/package.json test