@10x-media/undo-redo 0.1.0-beta.0

package/dist/client/formatShortcut.js

@@ -0,0 +1,113 @@
+//#region src/client/formatShortcut.ts
+/**
+* Render a `react-hotkeys-hook` chord the way the host platform writes it, so
+* tooltips describe the shortcut that is actually bound. A hardcoded "Ctrl+Z" is
+* wrong on macOS, and wrong everywhere once a host overrides `shortcuts`.
+*
+* Parsing mirrors react-hotkeys-hook's own `parseHotkeys`: the same split keys,
+* the same alias table, the same reserved modifier list. Whatever the library
+* binds as a modifier is drawn as one, and whatever it binds as a key is drawn
+* as a key, so the label can never disagree with the binding.
+*/
+/** Chord parts read as modifiers rather than keys. */
+const MODIFIERS = [
+	"shift",
+	"alt",
+	"meta",
+	"mod",
+	"ctrl",
+	"control"
+];
+/** Modifier order both Apple and Microsoft use in their own shortcut labels. */
+const MODIFIER_ORDER = [
+	"ctrl",
+	"alt",
+	"shift",
+	"meta"
+];
+/**
+* Key aliases react-hotkeys-hook accepts, normalized to its canonical names.
+* Its alias table also covers physical codes (`ControlLeft`, `ShiftRight`),
+* which exist for matching `event.code` and are not a form anyone writes in a
+* config, so they are left out here.
+*/
+const KEY_ALIASES = {
+	down: "arrowdown",
+	esc: "escape",
+	left: "arrowleft",
+	return: "enter",
+	right: "arrowright",
+	up: "arrowup"
+};
+const MAC_MODIFIER_LABELS = {
+	alt: "⌥",
+	ctrl: "⌃",
+	meta: "⌘",
+	shift: "⇧"
+};
+const MODIFIER_LABELS = {
+	alt: "Alt",
+	ctrl: "Ctrl",
+	meta: "Meta",
+	shift: "Shift"
+};
+/** Keys whose name reads worse than the glyph every platform prints on the cap. */
+const KEY_LABELS = {
+	arrowdown: "↓",
+	arrowleft: "←",
+	arrowright: "→",
+	arrowup: "↑",
+	escape: "Esc"
+};
+const MAC_KEY_LABELS = {
+	backspace: "⌫",
+	delete: "⌦",
+	enter: "↩",
+	escape: "⎋",
+	tab: "⇥"
+};
+const SPLIT_KEY = "+";
+const SEQUENCE_SPLIT_KEY = ">";
+/**
+* Lowercased before the alias lookup, not after, because the library lowercases
+* the whole chord before it maps anything. Looking `Left` up in a lowercase
+* alias table misses, and `mod+Left` would then be drawn as `Left` while the
+* binding listens for `arrowleft`.
+*/
+const normalizePart = (part) => {
+	const key = part.trim().toLowerCase();
+	return (KEY_ALIASES[key] ?? key).replace(/key|digit|numpad/, "");
+};
+const isModifier = (part) => MODIFIERS.includes(part);
+const keyLabel = (key, isMac) => {
+	const named = (isMac ? MAC_KEY_LABELS[key] : void 0) ?? KEY_LABELS[key];
+	if (named) return named;
+	return key.charAt(0).toUpperCase() + key.slice(1);
+};
+const formatChord = (chord, isMac) => {
+	const parts = chord.split(SPLIT_KEY).map(normalizePart).filter(Boolean);
+	const present = new Set(parts.filter(isModifier));
+	if (present.has("mod")) present.add(isMac ? "meta" : "ctrl");
+	if (present.has("control")) present.add("ctrl");
+	const modifiers = MODIFIER_ORDER.filter((modifier) => present.has(modifier)).map((modifier) => (isMac ? MAC_MODIFIER_LABELS : MODIFIER_LABELS)[modifier] ?? modifier);
+	const pressed = parts.filter((part) => !isModifier(part)).map((key) => keyLabel(key, isMac));
+	return [...modifiers, ...pressed].join(isMac ? "" : "+");
+};
+/**
+* Human-readable form of one chord, e.g. `mod+shift+z` as `⇧⌘Z` on macOS and
+* `Ctrl+Shift+Z` elsewhere. Sequences (`g>h`) render as their steps in order.
+*/
+const formatShortcut = (chord, isMac) => chord.split(SEQUENCE_SPLIT_KEY).map((step) => formatChord(step, isMac)).filter(Boolean).join(" ");
+/**
+* The platform test react-hotkeys-hook itself applies to resolve `mod`, copied
+* rather than imported because the library does not export it. Diverging here
+* would label a chord with a modifier other than the one it listens for.
+*/
+const isMacPlatform = () => {
+	if (typeof navigator === "undefined") return false;
+	return /mac/i.test(navigator.userAgent) && !/iphone|ipad|ipod/i.test(navigator.userAgent);
+};
+//#endregion
+export { formatShortcut, isMacPlatform };
+
+//# sourceMappingURL=formatShortcut.js.map

package/dist/client/formatShortcut.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"formatShortcut.js","names":[],"sources":["../../src/client/formatShortcut.ts"],"sourcesContent":["/**\n * Render a `react-hotkeys-hook` chord the way the host platform writes it, so\n * tooltips describe the shortcut that is actually bound. A hardcoded \"Ctrl+Z\" is\n * wrong on macOS, and wrong everywhere once a host overrides `shortcuts`.\n *\n * Parsing mirrors react-hotkeys-hook's own `parseHotkeys`: the same split keys,\n * the same alias table, the same reserved modifier list. Whatever the library\n * binds as a modifier is drawn as one, and whatever it binds as a key is drawn\n * as a key, so the label can never disagree with the binding.\n */\n\n/** Chord parts read as modifiers rather than keys. */\nconst MODIFIERS = ['shift', 'alt', 'meta', 'mod', 'ctrl', 'control'] as const\n\ntype Modifier = (typeof MODIFIERS)[number]\n\n/** Modifier order both Apple and Microsoft use in their own shortcut labels. */\nconst MODIFIER_ORDER = ['ctrl', 'alt', 'shift', 'meta'] as const\n\n/**\n * Key aliases react-hotkeys-hook accepts, normalized to its canonical names.\n * Its alias table also covers physical codes (`ControlLeft`, `ShiftRight`),\n * which exist for matching `event.code` and are not a form anyone writes in a\n * config, so they are left out here.\n */\nconst KEY_ALIASES: Record<string, string> = {\n\tdown: 'arrowdown',\n\tesc: 'escape',\n\tleft: 'arrowleft',\n\treturn: 'enter',\n\tright: 'arrowright',\n\tup: 'arrowup',\n}\n\nconst MAC_MODIFIER_LABELS: Record<string, string> = {\n\talt: '⌥',\n\tctrl: '⌃',\n\tmeta: '⌘',\n\tshift: '⇧',\n}\n\nconst MODIFIER_LABELS: Record<string, string> = {\n\talt: 'Alt',\n\tctrl: 'Ctrl',\n\tmeta: 'Meta',\n\tshift: 'Shift',\n}\n\n/** Keys whose name reads worse than the glyph every platform prints on the cap. */\nconst KEY_LABELS: Record<string, string> = {\n\tarrowdown: '↓',\n\tarrowleft: '←',\n\tarrowright: '→',\n\tarrowup: '↑',\n\tescape: 'Esc',\n}\n\nconst MAC_KEY_LABELS: Record<string, string> = {\n\tbackspace: '⌫',\n\tdelete: '⌦',\n\tenter: '↩',\n\tescape: '⎋',\n\ttab: '⇥',\n}\n\nconst SPLIT_KEY = '+'\nconst SEQUENCE_SPLIT_KEY = '>'\n\n/**\n * Lowercased before the alias lookup, not after, because the library lowercases\n * the whole chord before it maps anything. Looking `Left` up in a lowercase\n * alias table misses, and `mod+Left` would then be drawn as `Left` while the\n * binding listens for `arrowleft`.\n */\nconst normalizePart = (part: string): string => {\n\tconst key = part.trim().toLowerCase()\n\treturn (KEY_ALIASES[key] ?? key).replace(/key|digit|numpad/, '')\n}\n\nconst isModifier = (part: string): part is Modifier => MODIFIERS.includes(part as Modifier)\n\nconst keyLabel = (key: string, isMac: boolean): string => {\n\tconst named = (isMac ? MAC_KEY_LABELS[key] : undefined) ?? KEY_LABELS[key]\n\tif (named) return named\n\treturn key.charAt(0).toUpperCase() + key.slice(1)\n}\n\nconst formatChord = (chord: string, isMac: boolean): string => {\n\tconst parts = chord.split(SPLIT_KEY).map(normalizePart).filter(Boolean)\n\tconst present = new Set(parts.filter(isModifier))\n\t// `mod` is the library's platform alias and `control` its long spelling;\n\t// both collapse onto a canonical modifier before anything is drawn.\n\tif (present.has('mod')) present.add(isMac ? 'meta' : 'ctrl')\n\tif (present.has('control')) present.add('ctrl')\n\n\tconst modifiers = MODIFIER_ORDER.filter((modifier) => present.has(modifier)).map(\n\t\t(modifier) => (isMac ? MAC_MODIFIER_LABELS : MODIFIER_LABELS)[modifier] ?? modifier\n\t)\n\tconst pressed = parts.filter((part) => !isModifier(part)).map((key) => keyLabel(key, isMac))\n\n\t// macOS prints modifier glyphs run together, everything else separates them.\n\treturn [...modifiers, ...pressed].join(isMac ? '' : '+')\n}\n\n/**\n * Human-readable form of one chord, e.g. `mod+shift+z` as `⇧⌘Z` on macOS and\n * `Ctrl+Shift+Z` elsewhere. Sequences (`g>h`) render as their steps in order.\n */\nexport const formatShortcut = (chord: string, isMac: boolean): string =>\n\tchord\n\t\t.split(SEQUENCE_SPLIT_KEY)\n\t\t.map((step) => formatChord(step, isMac))\n\t\t.filter(Boolean)\n\t\t.join(' ')\n\n/**\n * The platform test react-hotkeys-hook itself applies to resolve `mod`, copied\n * rather than imported because the library does not export it. Diverging here\n * would label a chord with a modifier other than the one it listens for.\n */\nexport const isMacPlatform = (): boolean => {\n\tif (typeof navigator === 'undefined') return false\n\treturn /mac/i.test(navigator.userAgent) && !/iphone|ipad|ipod/i.test(navigator.userAgent)\n}\n"],"mappings":";;;;;;;;;;;;AAYA,MAAM,YAAY;CAAC;CAAS;CAAO;CAAQ;CAAO;CAAQ;AAAS;;AAKnE,MAAM,iBAAiB;CAAC;CAAQ;CAAO;CAAS;AAAM;;;;;;;AAQtD,MAAM,cAAsC;CAC3C,MAAM;CACN,KAAK;CACL,MAAM;CACN,QAAQ;CACR,OAAO;CACP,IAAI;AACL;AAEA,MAAM,sBAA8C;CACnD,KAAK;CACL,MAAM;CACN,MAAM;CACN,OAAO;AACR;AAEA,MAAM,kBAA0C;CAC/C,KAAK;CACL,MAAM;CACN,MAAM;CACN,OAAO;AACR;;AAGA,MAAM,aAAqC;CAC1C,WAAW;CACX,WAAW;CACX,YAAY;CACZ,SAAS;CACT,QAAQ;AACT;AAEA,MAAM,iBAAyC;CAC9C,WAAW;CACX,QAAQ;CACR,OAAO;CACP,QAAQ;CACR,KAAK;AACN;AAEA,MAAM,YAAY;AAClB,MAAM,qBAAqB;;;;;;;AAQ3B,MAAM,iBAAiB,SAAyB;CAC/C,MAAM,MAAM,KAAK,KAAK,EAAE,YAAY;CACpC,QAAQ,YAAY,QAAQ,KAAK,QAAQ,oBAAoB,EAAE;AAChE;AAEA,MAAM,cAAc,SAAmC,UAAU,SAAS,IAAgB;AAE1F,MAAM,YAAY,KAAa,UAA2B;CACzD,MAAM,SAAS,QAAQ,eAAe,OAAO,KAAA,MAAc,WAAW;CACtE,IAAI,OAAO,OAAO;CAClB,OAAO,IAAI,OAAO,CAAC,EAAE,YAAY,IAAI,IAAI,MAAM,CAAC;AACjD;AAEA,MAAM,eAAe,OAAe,UAA2B;CAC9D,MAAM,QAAQ,MAAM,MAAM,SAAS,EAAE,IAAI,aAAa,EAAE,OAAO,OAAO;CACtE,MAAM,UAAU,IAAI,IAAI,MAAM,OAAO,UAAU,CAAC;CAGhD,IAAI,QAAQ,IAAI,KAAK,GAAG,QAAQ,IAAI,QAAQ,SAAS,MAAM;CAC3D,IAAI,QAAQ,IAAI,SAAS,GAAG,QAAQ,IAAI,MAAM;CAE9C,MAAM,YAAY,eAAe,QAAQ,aAAa,QAAQ,IAAI,QAAQ,CAAC,EAAE,KAC3E,cAAc,QAAQ,sBAAsB,iBAAiB,aAAa,QAC5E;CACA,MAAM,UAAU,MAAM,QAAQ,SAAS,CAAC,WAAW,IAAI,CAAC,EAAE,KAAK,QAAQ,SAAS,KAAK,KAAK,CAAC;CAG3F,OAAO,CAAC,GAAG,WAAW,GAAG,OAAO,EAAE,KAAK,QAAQ,KAAK,GAAG;AACxD;;;;;AAMA,MAAa,kBAAkB,OAAe,UAC7C,MACE,MAAM,kBAAkB,EACxB,KAAK,SAAS,YAAY,MAAM,KAAK,CAAC,EACtC,OAAO,OAAO,EACd,KAAK,GAAG;;;;;;AAOX,MAAa,sBAA+B;CAC3C,IAAI,OAAO,cAAc,aAAa,OAAO;CAC7C,OAAO,OAAO,KAAK,UAAU,SAAS,KAAK,CAAC,oBAAoB,KAAK,UAAU,SAAS;AACzF"}

package/dist/client/historyDebugOverlay.css

@@ -0,0 +1,206 @@
+/* Developer overlay, not editor chrome: it deliberately floats above the admin
+   UI instead of docking into a Payload slot, so it stays usable while the form
+   below is scrolled and edited. Colors come from Payload's theme tokens so it
+   follows light/dark without a second stylesheet. */
+.undo-redo-debug {
+	position: fixed;
+	right: 1rem;
+	bottom: 1rem;
+	z-index: 100;
+	display: flex;
+	flex-direction: column;
+	width: min(560px, calc(100vw - 2rem));
+	max-height: min(60vh, 640px);
+	overflow: hidden;
+	border: 1px solid var(--theme-elevation-150);
+	border-radius: var(--style-radius-m);
+	background: var(--theme-elevation-0);
+	color: var(--theme-elevation-800);
+	font-family: var(--font-mono);
+	font-size: 12px;
+	line-height: 1.5;
+	box-shadow: 0 8px 24px -8px rgba(0, 0, 0, 0.35);
+	resize: both;
+}
+
+.undo-redo-debug__header {
+	display: flex;
+	flex-shrink: 0;
+	align-items: center;
+	gap: 8px;
+	padding: 8px 10px;
+	border-bottom: 1px solid var(--theme-elevation-150);
+	background: var(--theme-elevation-50);
+}
+
+.undo-redo-debug__title {
+	font-family: var(--font-body);
+}
+
+.undo-redo-debug__meta {
+	margin-right: auto;
+	color: var(--theme-elevation-500);
+}
+
+.undo-redo-debug__action {
+	padding: 2px 8px;
+	border: 1px solid var(--theme-elevation-150);
+	border-radius: var(--style-radius-s);
+	background: var(--theme-elevation-0);
+	color: inherit;
+	font-family: inherit;
+	font-size: inherit;
+	cursor: pointer;
+}
+
+.undo-redo-debug__action:hover {
+	border-color: var(--theme-elevation-250);
+	background: var(--theme-elevation-100);
+}
+
+.undo-redo-debug__body {
+	flex: 1;
+	overflow-y: auto;
+	padding: 4px 0;
+}
+
+.undo-redo-debug__empty {
+	margin: 0;
+	padding: 12px 10px;
+	color: var(--theme-elevation-500);
+}
+
+.undo-redo-debug__entry {
+	border-bottom: 1px solid var(--theme-elevation-100);
+}
+
+/* The entry matching the form state on screen right now. */
+.undo-redo-debug__entry--current {
+	background: var(--theme-elevation-50);
+	box-shadow: inset 3px 0 0 var(--theme-success-500);
+}
+
+/* Edits made but still inside the capture debounce, so not an entry yet. */
+.undo-redo-debug__entry--pending {
+	box-shadow: inset 3px 0 0 var(--theme-warning-500);
+}
+
+.undo-redo-debug__entryHead {
+	display: flex;
+	align-items: center;
+	gap: 6px;
+	padding-right: 8px;
+}
+
+.undo-redo-debug__toggle {
+	display: flex;
+	flex: 1;
+	align-items: center;
+	gap: 6px;
+	min-width: 0;
+	padding: 6px 8px;
+	border: 0;
+	background: none;
+	color: inherit;
+	font-family: inherit;
+	font-size: inherit;
+	text-align: left;
+	cursor: pointer;
+}
+
+.undo-redo-debug__caret {
+	width: 10px;
+	color: var(--theme-elevation-400);
+}
+
+.undo-redo-debug__index {
+	flex-shrink: 0;
+	color: var(--theme-elevation-500);
+}
+
+.undo-redo-debug__summary {
+	overflow: hidden;
+	white-space: nowrap;
+	text-overflow: ellipsis;
+}
+
+.undo-redo-debug__count {
+	flex-shrink: 0;
+	margin-left: auto;
+	padding: 0 6px;
+	border-radius: var(--style-radius-s);
+	background: var(--theme-elevation-100);
+	color: var(--theme-elevation-600);
+}
+
+.undo-redo-debug__jump {
+	flex-shrink: 0;
+	padding: 2px 6px;
+	border: 1px solid var(--theme-elevation-150);
+	border-radius: var(--style-radius-s);
+	background: var(--theme-elevation-0);
+	color: inherit;
+	font-family: inherit;
+	font-size: 11px;
+	cursor: pointer;
+}
+
+.undo-redo-debug__jump:disabled {
+	opacity: 0.4;
+	cursor: default;
+}
+
+.undo-redo-debug__diff {
+	width: 100%;
+	margin: 0 0 6px;
+	padding: 0 8px 0 24px;
+	border-collapse: collapse;
+	table-layout: fixed;
+}
+
+.undo-redo-debug__diff td {
+	padding: 1px 4px;
+	overflow: hidden;
+	vertical-align: top;
+	white-space: nowrap;
+	text-overflow: ellipsis;
+}
+
+.undo-redo-debug__path {
+	width: 34%;
+	color: var(--theme-elevation-700);
+}
+
+.undo-redo-debug__presence {
+	margin-left: 4px;
+	padding: 0 4px;
+	border-radius: var(--style-radius-s);
+	background: var(--theme-elevation-100);
+	color: var(--theme-elevation-500);
+	font-size: 10px;
+}
+
+.undo-redo-debug__from {
+	width: 29%;
+	color: var(--theme-error-500);
+}
+
+.undo-redo-debug__arrow {
+	width: 16px;
+	color: var(--theme-elevation-400);
+}
+
+.undo-redo-debug__to {
+	width: 29%;
+	color: var(--theme-success-500);
+}
+
+/* The entry that matches the persisted document. */
+.undo-redo-debug__saved {
+	flex-shrink: 0;
+	padding: 0 4px;
+	border-radius: var(--style-radius-s);
+	background: var(--theme-success-100);
+	color: var(--theme-success-600);
+	font-size: 10px;
+}

package/dist/client/undoRedoControls.css

@@ -0,0 +1,58 @@
+/* The controls mount inside Payload's document controls, next to Save/Publish.
+   Payload's Button sizes itself from text padding, which makes an icon-only
+   button a wide rounded rectangle. These are squared off to the same box as the
+   row's own icon button (the kebab menu: 1.6 * base, matching the height of a
+   medium button) so the group reads as toolbar chrome rather than as three text
+   buttons that happen to hold icons.
+
+   `--undo-redo-control-size` is the one knob for hosts mounting the controls
+   somewhere tighter than the document controls. */
+.undo-redo-controls {
+	--undo-redo-control-size: calc(var(--base) * 1.6);
+	--undo-redo-icon-size: calc(var(--base) * 0.9);
+
+	display: flex;
+	align-items: center;
+	gap: calc(var(--base) * 0.2);
+}
+
+/* Doubled class so the padding reset outranks Payload's own `.btn--size-*`
+   rules whichever order the two stylesheets end up in. */
+.undo-redo-controls__button.btn {
+	--btn-padding-block-start: 0;
+	--btn-padding-block-end: 0;
+	--btn-padding-inline-start: 0;
+	--btn-padding-inline-end: 0;
+
+	display: flex;
+	align-items: center;
+	justify-content: center;
+	width: var(--undo-redo-control-size);
+	height: var(--undo-redo-control-size);
+}
+
+.undo-redo-controls__button.btn svg {
+	width: var(--undo-redo-icon-size);
+	height: var(--undo-redo-icon-size);
+}
+
+/* Disabled has to be readable across three squares sitting side by side, and a
+   muted icon alone is not enough at this size. So the fill and the enabled
+   border are dropped while the outline stays: the square keeps its place in the
+   row, but reads as an empty slot rather than a pressable control.
+
+   Payload's subtle style derives its hover variables from `--bg-color`,
+   `--btn-border` and `--color`, all overridden here, so hover stays flat
+   without restating it. */
+.undo-redo-controls__button.btn.btn--disabled {
+	--bg-color: transparent;
+	--btn-border: 1px solid var(--theme-elevation-100);
+	--color: var(--theme-elevation-350);
+}
+
+/* Held-open state, mirroring how the document controls mark their own popup
+   trigger while its menu is showing. */
+.undo-redo-controls__button--active.btn {
+	--bg-color: var(--theme-elevation-150);
+	--btn-border: 1px solid var(--theme-elevation-400);
+}

package/dist/client/useUndoRedo.d.ts

@@ -0,0 +1,70 @@
+import { UndoHistory } from "../history/historyCore.js";
+import { ControlsClientProps } from "../plugin/options.js";
+import { FormState } from "payload";
+
+//#region src/client/useUndoRedo.d.ts
+/**
+ * Every setting is optional so the hook stays usable when a host calls it by
+ * hand rather than through the plugin, which always passes a fully resolved set.
+ */
+type UseUndoRedoOptions = Partial<ControlsClientProps>;
+/** The chords actually bound, or null when keyboard handling is off. */
+interface BoundChords {
+  undo: string[];
+  redo: string[];
+}
+interface UseUndoRedoResult {
+  /** True when there is an earlier entry to step back to. */
+  canUndo: boolean;
+  /** True when there is a later entry to step forward to. */
+  canRedo: boolean;
+  undo: () => void;
+  redo: () => void;
+  /** Restore the entry at `index` in `history.stack`. Out-of-range indexes no-op. */
+  jumpTo: (index: number) => void;
+  /** Live form state, as `useAllFormFields` reports it. */
+  fields: FormState;
+  /**
+   * The mutable history object backing this instance.
+   *
+   * Exposed so a custom control can mount `<HistoryDebugOverlay />` or inspect
+   * the stack. It is an internal structure, not a stable contract: treat it as
+   * read-only and expect its shape to change in a minor release.
+   */
+  history: UndoHistory;
+  /**
+   * Counter bumped on every capture and restore. Only moves when `debug` is on,
+   * since it exists to pull the mutable history into React's render cycle for
+   * the inspector and nothing else needs the re-renders.
+   */
+  revision: number;
+  /** False under autosave, where the saved baseline is deliberately not tracked. */
+  tracksSavedState: boolean;
+  /** Resolved keyboard chords, for labelling. Null when `shortcuts` is false. */
+  chords: BoundChords | null;
+}
+/**
+ * Undo/redo for the surrounding Payload form: a client-side history of
+ * form-state snapshots, independent of Payload's document versions, with
+ * nothing read from or written to the server until the user saves.
+ *
+ * Backs `<UndoRedoControls />` and is exported so a host can build its own
+ * controls instead (pair it with `autoMount: false`). Must be called from
+ * inside a document edit form; outside one it finds no fields and stays
+ * disabled.
+ *
+ * One history per call. Two instances on the same form keep two independent
+ * stacks and each captures the other's restores as fresh edits, so mount either
+ * ours or yours, not both.
+ */
+declare const useUndoRedo: ({
+  captureDebounce,
+  debug,
+  ignoreFieldTypes,
+  ignorePaths,
+  maxHistory,
+  shortcuts
+}?: UseUndoRedoOptions) => UseUndoRedoResult;
+//#endregion
+export { BoundChords, UseUndoRedoOptions, UseUndoRedoResult, useUndoRedo };
+//# sourceMappingURL=useUndoRedo.d.ts.map