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

locate-config-kt

v1.3.0

Published

Find a utility/package config

Readme

locate-config-kt

A lightweight Node.js utility for reliably locating and reading configuration files from your project’s root, src, or config directories.
Includes built-in caching and async file resolution support.


📦 Installation

npm install locate-config-kt find-root-kt
# or
yarn add locate-config-kt find-root-kt

🚀 Usage

import { getConfig, clearConfigCache } from "locate-config-kt";

const config = await getConfig({
  configFileNameWithExtension: "config.json",
});

if (config) {
  console.log("Config loaded:", config.toString());
} else {
  console.log("No config file found!");
}

🧠 How It Works

locate-config-kt searches for a configuration file in the following order:

  1. Project root/<projectRoot>/<filename>
  2. Root src folder/<projectRoot>/src/<filename>
  3. Config folder/<projectRoot>/config/<filename>
  4. Config under src/<projectRoot>/src/config/<filename>

It uses find-root-kt to determine the actual project root dynamically.


⚙️ API Reference

getConfig(options): Promise<string | null>

Asynchronously searches and reads a configuration file.
If found, returns its contents (as a UTF-8 string by default).
If not found, returns null.

Parameters

| Name | Type | Default | Description | |------|------|----------|-------------| | configFileNameWithExtension | string | required | The name of the configuration file, e.g. "tsconfig.json". | | cache | boolean | true | Enables in-memory caching for faster subsequent reads. | | srcDirName | string | "src" | Name of your source directory to check for configs. | | encoding | "ascii" \| "utf8" \| "utf-8" \| "utf16le" \| "utf-16le" \| "ucs2" \| "ucs-2" \| "base64" | "utf-8" | File encoding when reading the configuration. |

Example

import { getConfig } from "locate-config-kt";

// Load tsconfig.json
const tsConfig = await getConfig({ configFileNameWithExtension: "tsconfig.json" });
console.log(tsConfig?.toString());

// Load .env from src/config directory
const envFile = await getConfig({
  configFileNameWithExtension: ".env",
  srcDirName: "src",
});
console.log(envFile?.toString());

clearConfigCache(): void

Clears the internal cache used by getConfig.
Useful if you modify or replace configuration files at runtime.

Example

import { clearConfigCache, getConfig } from "locate-config-kt";

await getConfig({ configFileNameWithExtension: "app.json" });
clearConfigCache(); // removes cached entries

🧩 Types

type UnwrapPromise<P> = P extends Promise<infer R> ? R : P;
type ReadValueType = UnwrapPromise<ReturnType<typeof readFile>>;
export type ConfigFileReadType = ReadValueType;

These internal types define the resolved type of file contents when using getConfig.


🪄 Example Project Structure

my-project/
├─ src/
│  ├─ config/
│  │  └─ app.json
│  └─ index.ts
├─ config/
│  └─ db.json
├─ package.json
└─ tsconfig.json

✅ Example

import { getConfig } from "locate-config-kt";

async function example() {
  const dbConfig = await getConfig({
    configFileNameWithExtension: "db.json",
  });

  if (dbConfig) {
    console.log("Database config:", dbConfig.toString());
  } else {
    console.warn("Database config not found!");
  }
}

example();