/**
 * Common ignore patterns for glob operations across Motoko files.
 *
 * The trailing `/**` only prunes entries *below* the ignored directory, so an
 * ignore glob can never prune at a checkout boundary — a nested repo root sits
 * next to its `.git`, not under it. See `isNestedCheckout`.
 *
 * `build`/`bundle` are not mops output; they are dirs users may still have
 * lying around from other tooling, and they hold copies of the project's
 * sources. Widen `isIgnoredDir` alongside this list.
 */
export declare const MOTOKO_IGNORE_PATTERNS: string[];
/**
 * Common glob configuration for Motoko file operations
 */
export declare const MOTOKO_GLOB_CONFIG: {
    nocase: boolean;
    ignore: string[];
};
/**
 * True when any ancestor of `absPath` strictly below `rootDir` is its own
 * checkout — a linked git worktree, a submodule, or a plain nested clone.
 *
 * Such a directory holds a `.git` entry that is a file (worktree, submodule)
 * or a directory (clone), and `MOTOKO_IGNORE_PATTERNS` prunes neither the
 * directory itself nor anything beside it, so its sources would otherwise be
 * picked up as the project's.
 */
export declare function isNestedCheckout(absPath: string, rootDir: string): boolean;
/**
 * True when `absPath` is inside one of the build/dependency directories that
 * `MOTOKO_IGNORE_PATTERNS` prunes for glob callers.
 *
 * chokidar's `ignored` takes a predicate, and a chokidar predicate *replaces*
 * glob-based ignoring rather than adding to it — so the watchers need the
 * pruning rule expressed as a path test, not just `isNestedCheckout`.
 */
export declare function isIgnoredDir(absPath: string, rootDir: string): boolean;
/**
 * Regex to match a file path for dependency and toolchain versions
 */
export declare const FILE_PATH_REGEX: RegExp;