/**
 * The refusal a deploy gives when the app's own module path does not reach
 * the OpenNext builder, and the cure it names.
 *
 * A project that installs `fjall` locally can still lack the builder. When npm
 * keeps a project's `next` that is outside the `next` peer range of the
 * builder release it resolves for `fjall`, as it keeps an exact pin below that
 * range, it installs that release inside `fjall`'s own node_modules, with a
 * `next` of its own, unless the project sets `legacy-peer-deps`. Installing
 * the builder in the project then fails with ERESOLVE while the project's
 * declared `next` admits no release in that range, as an exact pin below it
 * does (measured with npm 10.9.9 and 11.17.0 on 2026-10-04). Every version and
 * range the refusal prints is read from the installed packages, never spelled
 * here.
 */
export declare const OPENNEXT_PACKAGE = "@opennextjs/aws";
/**
 * Why the builder is missing from the app's module path (`searchPaths`, the
 * walk the builder was looked up on), and what installs it there.
 *
 * Only a builder npm nested inside the `fjall` the app resolves counts as
 * installed for fjall: a global `fjall`, or none, leaves the cure as installing
 * the builder in the project, and so does a copy on the app's path that the
 * lookup passed over because its `open-next` binary is missing.
 */
export declare function describeMissingOpenNextBuilder(searchPaths: readonly string[]): string;