import { fsm2 } from "@heydovetail/ui-components";
import { Plugin, Transaction } from "prosemirror-state";
import { Range } from "./types";
import { Step } from "prosemirror-transform";
interface PluginState {
    readonly type: "default";
    /**
     * Ranges sorted by `range.from`.
     */
    readonly sortedRanges: ReadonlyArray<Range>;
}
export declare const updateRangesFromSteps: (sortedRanges: ReadonlyArray<Range>, steps: Step<any>[]) => ReadonlyArray<Range>;
export declare const transition: <CurrentStateShape extends PluginState>(state: CurrentStateShape) => CurrentStateShape extends PluginState ? fsm2.Transition<PluginState, CurrentStateShape, {
    default: {
        tr: (prev: PluginState, { tr }: {
            tr: Transaction<any>;
        }) => {
            type: "default";
            sortedRanges: ReadonlyArray<Range>;
        };
    };
}, {
    default: {
        tr: (prev: PluginState, { tr }: {
            tr: Transaction<any>;
        }) => {
            type: "default";
            sortedRanges: ReadonlyArray<Range>;
        };
    };
} extends { [key in CurrentStateShape["type"]]: infer T; } ? T : never> : never;
declare const getPluginStateOrThrow: (source: import("prosemirror-state").EditorState<any> | Transaction<import("prosemirror-model").Schema<import("../schema").NodeTypeName, import("../schema").MarkTypeName>>) => PluginState;
export { PluginState, getPluginStateOrThrow };
/**
 * Track ranges in a document.
 *
 * This is kept as its own plugin (and not merged with `HighlightPlugin`)
 * primarily because it's anticipated that comments will use the same range
 * infrastructure as highlights, and so having ranges be managed by a single
 * dedicated plugin with its own transform steps avoids coupling to any
 * particular usage.
 */
export declare class RangePlugin extends Plugin {
    constructor(ranges?: ReadonlyArray<Range>, scrollToRangeId?: string);
}