export interface FederationFreshness {
    /** Record the outcome of a watcher-driven federation rebuild. */
    mark(success: boolean): void;
    /**
     * True when the Angular output being consumed now needs no federation rebuild.
     * Clears the flag either way — it only vouches for the window since the last
     * consumed Angular output, so it must be consumed with that output rather than
     * at the point a rebuild would run.
     */
    consume(dirtyPathCount: number | undefined): boolean;
}
export declare function createFederationFreshness(): FederationFreshness;
/**
 * Whether a watcher wake-up should drive a federation-only rebuild. `undefined`
 * means no watcher, so nothing can be pending.
 */
export declare function shouldRunWatcherRebuild(first: boolean, dirtyPathCount: number | undefined): boolean;
/**
 * Whether a changed path has to wake the federation rebuild directly, because
 * Angular's iterator will not emit for it.
 *
 * `watchedFiles` is what the last federation build compiled. `wakeDirs` covers
 * what that set cannot: linked shared packages (externals to the app build) and
 * shared-mapping source dirs, where a *newly created* file is by definition
 * absent from any compiled-inputs set and is not yet imported by the app.
 *
 * Core's `isUnderAnyDir` rather than a `path.sep` comparison: it delivers posix
 * paths, so splicing in the native separator is always false on Windows.
 *
 * `outputPath` is excluded first. A wake dir is the directory of a mapping's
 * resolved entry point, so a mapping whose entry point sits beside the build
 * output yields a wake dir that contains it — and a rebuild writes there with a
 * fresh mtime, which is no replay, so the loop would wake itself forever.
 * Filtering the event rather than dropping the dir keeps that dir's real sources
 * woken.
 */
export declare function shouldWakeFederation(changedPath: string, watchedFiles: ReadonlySet<string>, wakeDirs: readonly string[], outputPath: string): boolean;
//# sourceMappingURL=watch-decisions.d.ts.map