seniority/config

import { deepMerge, lineOf, packageLayer, … } from 'seniority/config';

function candidates(d: Discovery): {
    path: string;
    reason: string;
}[];

function deepMerge(base: Record<string, unknown>, over: Record<string, unknown>): Record<string, unknown>;

function discover(d: Discovery): Promise<Loaded | undefined>;

function lineOf(text: string, key: string): number | undefined;

function loadWithExtends(path: string, options?: LoadConfigOptions, seen?: string[]): Promise<Loaded>;

function packageLayer(path: string, name: string, manifest?: Record<string, unknown>): Layer | undefined;

interface Discovery {
    name: string;
    cwd: string;
    env: Record<string, string | undefined>;
    /** `--config <path>`. */
    explicit?: string;
    /** `--no-config`. */
    disabled?: boolean;
    /** Extra loaders, by extension, merged over the four builtins (R6). */
    loaders?: Readonly<Record<string, Loader>>;
    /**
     * The extensions tried in the current directory, in order. Defaults to the four Node can
     * read; a program that injected a `.yaml` loader adds `.yaml` here. The two are separate
     * because supplying a parser and asking discovery to look for that format are different
     * decisions, and a program may want either without the other.
     */
    extensions?: readonly string[];
    /**
     * Walk up from `cwd` looking for the same names (R5). **Off by default**: a config found
     * in a directory the user did not name is the kind of surprise `--explain` exists to
     * prevent, so it is a program's decision rather than an ambient behaviour.
     */
    upward?: boolean;
    /** The highest directory an upward walk may look in, inclusive. Defaults to the filesystem root (Y10). */
    stopAt?: string;
}

interface LoadConfigOptions {
    loaders?: Readonly<Record<string, Loader>>;
}

interface Loaded extends Layer {
    /** The files merged, outermost first — what `--explain` shows. */
    chain: string[];
}