import { PropellerInfra } from '../../context/PropellerContext';
type InfraKey = keyof PropellerInfra;
/**
 * Resolves the Tier 1 (deps) + Tier 2 (scope) infrastructure props for a
 * component.
 *
 * Precedence: an explicit prop value (defined and non-null) always wins —
 * existing call sites keep working unchanged. Otherwise the value is taken
 * from the composite of plugin deps and `<PropellerProvider>` scope. Non-infra
 * props pass through untouched.
 *
 * Null-context safe: with no plugin or no provider the props are returned
 * as-is, so components still work standalone / in tests.
 *
 * MUST be called from `setup()` — Vue's `inject()` only works there. Calling
 * this lazily from inside a `computed` getter, an effect, or a click handler
 * yields `null` for the provider context (and a console warning), which is
 * what the previous "wrap in computed" pattern caused for any prop that hadn't
 * been read synchronously during setup.
 *
 * The returned object is a `reactive` proxy whose infra-key reads always
 * reflect (explicit prop OR provider snapshot OR undefined). Non-infra props
 * pass through unchanged via getter forwarding, so consumers can iterate or
 * destructure it as they would a plain object.
 */
export declare function useInfraProps<P extends Partial<Record<InfraKey, unknown>>>(props: P): P & Partial<PropellerInfra>;
export {};