tiptap-markdown-react 0.17.1 → 0.18.0

package/README.md

@@ -295,14 +295,34 @@ Override any of these CSS variables on an ancestor (e.g. `:root` or the editor c
 | `findBarOffset` | `{ top?, right?, bottom?, left? } \| number = px` | Where the library-rendered bar sits inside its positioning context. Default `{ top: 4, right: 4 }` (top-right); pass e.g. `{ bottom: 8, left: 8 }` to dock it elsewhere. The context is the editor, or your `findBarContainer` element when you supply one — the library adds `position: relative` to that container if it is `static` (otherwise the bar would anchor to some unexpected ancestor). |
 | `findShortcut` | `boolean` | Take over <kbd>Cmd/Ctrl</kbd>+<kbd>F</kbd> while the editor has focus (default `true`; bound only when the editor owns a bar). `false` keeps the browser's native find — wire your own entry with `handle.openFind()`. |
 | `findLabels` | `Partial<FindLabels>` | Localize the find & replace bar. |
+| `onFindOpenChange` | `(open: boolean) => void` | Fired when the bar actually shows or hides (Esc / × included). Use it to drive an external entry such as the toolbar magnifier. Fires only on a real change — never a `false` on mount — and stays `false` while `findBar={false}`, so a host-placed bar never lights up an entry you did not open. |
 | `className` | `string` | Class on the scroll container. |
 
 Ref handle (`MarkdownWysiwygEditorHandle`): `getMarkdown()`, `getHTML()`, `getJSON()`, `getEditor()`,
-`focusComment(id)`, `nextComment(dir?)`, `getCommentIds()`, `openFind()`, `closeFind()`.
+`focusComment(id)`, `nextComment(dir?)`, `getCommentIds()`, `openFind()`, `closeFind()`, `toggleFind()`.
+`openFind()` keeps the same "press again" feel as <kbd>Cmd/Ctrl</kbd>+<kbd>F</kbd> — refocus the search field and
+select the query — while `toggleFind()` flips the bar and pairs with an entry that shows an active state
+(`onSearch={() => handle.current?.toggleFind()}`).
 
 #### Find & replace
 
-<kbd>Cmd/Ctrl</kbd>+<kbd>F</kbd> (while focus is inside the editor) opens a floating bar: match counter inside the search field, wrap-around next/previous, match-case and whole-word toggles, replace and replace-all. `Esc` closes it, clears the highlights and returns focus to the editor. Read-only editors (`editable={false}`) can search but not replace.
+<kbd>Cmd/Ctrl</kbd>+<kbd>F</kbd> (while focus is inside the editor) opens a floating bar: match counter inside the search field, wrap-around next/previous, match-case and whole-word toggles, replace and replace-all. Read-only editors (`editable={false}`) can search but not replace. <kbd>Enter</kbd> in the search field jumps to the next match — but an <kbd>Enter</kbd> that is committing an IME candidate (Chinese/Japanese input) is left alone, so confirming a word never jumps or replaces.
+
+**Closing it.** `Esc` closes the bar, clears the highlights and returns focus to the editor; it works from anywhere that belongs to the editor (focus inside the bar, inside the document, or on the page while this is the only editor), and the keystroke is consumed so a host popover or drawer wrapping the bar does not close along with it. Other ways out: the bar's ×, `handle.closeFind()`, `toggleFind()`, and unmounting the bar. Deliberately **not** closing on: clicking into the document or another input, an empty query, zero results, after replace-all, or switching to read-only (search stays available then — only the replace row goes away). If an editor is swapped out (remounted for a new document), the library reports `onFindOpenChange(false)` so an entry elsewhere never stays lit.
+
+`<EditorToolbar>` can carry an entry to the same bar. Pass `onSearch` (wired to the ref handle) and the magnifier appears just left of the More menu; omit it and the button does not render. Feed `searchActive` from `onFindOpenChange` and it lights up while the bar is open — pair it with `toggleFind()` so the lit button also turns the bar back off:
+
+```tsx
+const find = useRef<MarkdownWysiwygEditorHandle>(null)
+const [findOpen, setFindOpen] = useState(false)
+
+<EditorToolbar
+  editor={editor}
+  onSearch={() => find.current?.toggleFind()}
+  searchActive={findOpen}
+/>
+<MarkdownWysiwygEditor ref={find} onFindOpenChange={setFindOpen} />
+```
 
 Matching is done by the official extension, so the semantics are its semantics — worth knowing before you rely on them:
 
@@ -352,13 +372,15 @@ With `findBar={false}` the editor does not bind <kbd>Cmd/Ctrl</kbd>+<kbd>F</kbd>
 
 `FindReplaceBar` is exported if you'd rather place the bar yourself, `FindLabels` / `defaultFindLabels` for i18n, and `FindAndReplace` for hand-built pipelines. Two details to reuse when driving it yourself: keep `searchDebounceMs: 0` on the extension and debounce in your own UI, and route calls through `runFindCommand()` — it absorbs a Tiptap 3.31.3 transaction mismatch that fires on the first search when the document ends with a code block / table / chart (see the comment on `runFindCommand` for the mechanism).
 
+Styling the bar from the outside: its internals use hashed CSS-module classes, so the bar carries stable hooks instead — `[data-find-bar]` on the root, `[data-find-field="search|replace"]` on the inputs, `[data-find-counter]` on the counter, `[data-find-option="match-case|whole-words"]` on the toggles and `[data-find-action="previous|next|close|replace|replace-all"]` on the buttons. Colors stay on the theme variables (`--tmr-find-*` for the highlights, `--tmr-toolbar-*` / `--tmr-accent` for the bar chrome).
+
 #### i18n (labels)
 
 There is no global locale and no provider: every visible string comes from a `Partial<XLabels>` prop that is merged over built-in English defaults (`{ ...defaultToolbarLabels, ...labels }`). A host ships one object per language and passes it down; switching languages is picking a different object. Override only the keys you care about — everything else falls back to English.
 
 | Component | Prop | Type |
 | --- | --- | --- |
-| `<EditorToolbar>` | `labels` | `Partial<ToolbarLabels>` (also covers the Import menu and the equation popover) |
+| `<EditorToolbar>` | `labels` | `Partial<ToolbarLabels>` (also covers the Import menu, the equation popover and the link popover) |
 | `<MarkdownWysiwygEditor>` | `findLabels` | `Partial<FindLabels>` (replace / replace-all appear as icon buttons, so their labels are the tooltip + accessible name) |
 | `<MarkdownWysiwygEditor>` | `codeBlockLabels` | `Partial<CodeBlockLabels>` |
 | `<TocPanel>` | `labels` | `Partial<TocLabels>` |
@@ -386,6 +408,8 @@ The underlying extensions `MarkdownPaste` / `MarkdownFileDrop` (and the `looksLi
 
 ### `<EditorToolbar>` (client)
 
+The row is centred and, when the controls no longer fit the container, **wraps onto a second line** rather than scrolling sideways — a hidden control is worse than a taller toolbar. The full set (search entry included) needs about 1045 px of container width; narrower containers get a wrapped line with 4 px of vertical breathing room. `onSearch` renders the magnifier just left of the More menu.
+
 | Prop | Type | Description |
 | --- | --- | --- |
 | `editor` | `Editor` | The instance from `onEditorReady`. |
@@ -396,9 +420,57 @@ The underlying extensions `MarkdownPaste` / `MarkdownFileDrop` (and the `looksLi
 | `importMenuItems` | `ImportMenuItem[]` | Import dropdown options (`label` + `accept`). Hosts that want Markdown / Word / PDF pass three items. |
 | `showImport` | `boolean` | Show the Import dropdown (default `true`). |
 | `labels` | `Partial<ToolbarLabels>` | i18n labels. |
+| `onSearch` | `() => void` | Search entry (magnifier) left of the More menu. Wire it to `handle.toggleFind()` (or `openFind()` if you'd rather it only ever open); omit it and no button renders. Worth passing only when the editor owns a bar (`findBar` on) — a host-placed bar has nothing for it to open. Search works read-only, so the button never greys out. |
+| `searchActive` | `boolean` | Whether the bar is open; drives `aria-pressed` and the active highlight of the search entry (default `false`). Feed it from the editor's `onFindOpenChange`. |
 | `extraToolbarItems` | `ExtraToolbarItem[]` | Custom items appended to the "More" menu. |
 | `labels.inlineMath` / `blockMath` | `string` | More-menu equation items. |
 | `labels.mathPlaceholder` / `mathDone` / `mathNewInline` / `mathNewBlock` | `string` | Equation editor (empty chip/hint, input, Done). |
+| `labels.tableRowMenu` / `tableColumnMenu` | `string` | Aria-labels of the table hover handles. |
+| `labels.linkPrompt` / `linkApply` / `linkOpen` / `linkRemove` / `linkInvalid` | `string` | Link popover: field placeholder, apply, open in new window, remove, rejected-address hint. |
+
+#### Table editing (hover handles)
+
+Hover any cell and four affordances appear: a `⋮` handle on the row's left edge, a `⋯` handle above the table aligned to the column, a `+` pill on the table's right edge (**append a column**) and a `+` pill below it (**append a row**). They are all sized to what they act on: the row handle spans the row's height, the column handle spans the column's width, and each `+` spans the table's edge it sits on. Clicking a handle selects that whole row / column and opens its menu: add before / after, delete, **Clear content**, **Reset cell styles**, plus **Delete table**. The handles ship with `<EditorToolbar>` (they are its table UI), reuse the same commands as the insert-table grid, and do not appear on read-only editors.
+
+Right-click is still wired for exactly one case: a **multi-cell selection** (drag across cells). A handle can only express one row or one column, so batch add/delete of a rectangle keeps the context menu.
+
+**Clear content** empties the selected cells but keeps them (a header row therefore never degrades into a data row), and **Reset cell styles** puts `colwidth` / `align` back to their schema defaults while leaving `colspan` / `rowspan` alone — those are structural, and the extension's `mergeCells` / `splitCell` are deliberately **not** exposed here: GFM has no `colspan`, so a merged cell exports as `| 1<br>2 |  |` and cannot be restored on reload. Column width is a *column* property managed by the resize plugin, so clearing it needs the whole column selected (from the row handle it is restored from the widest cell in that column, which is the plugin's normal behavior).
+
+Styling hooks (internals are hashed CSS-module classes): `[data-table-handle="row|col"]` on the handles, `[data-table-menu]` on the menu. Colors ride `--tmr-table-handle-bg` / `-fg` / `-border` (a light pill by default; hovering turns it into `--tmr-accent`).
+
+**Not included: dragging a handle to reorder rows or columns.** That is precisely the part the official `table-node` component implements inside its own source — which is a **paid** Start-plan component (the registry answers 401 for `table-node`, `toc-node`, `drag-context-menu` while free ones answer 200), so it cannot be vendored into this MIT package. The free `@tiptap/extension-table` ships the add/delete/header/merge commands used here but no move commands; reordering would be our own transaction code on top of `TableMap`.
+
+### `<LinkPopover>` (client)
+
+The toolbar's link button opens this popover — type an address, apply it, open it in a new window, or remove the link. With the caret inside a link it prefills that link's href, so editing a URL no longer means deleting and re-adding it (the old `window.prompt` also could not be edited, gave no feedback for a rejected address, and is unavailable in Electron and some WebViews).
+
+```tsx
+<LinkPopover
+  editor={editor}
+  labels={{ field: 'Paste a link…' }}
+  trigger={<button type="button" className="my-btn"><LinkIcon /></button>}
+/>
+```
+
+| Prop | Type | Description |
+| --- | --- | --- |
+| `editor` | `Editor` | The editor to operate on. |
+| `trigger` | `ReactNode` | Your own trigger element. Radix's `asChild` takes over its click / ref / aria, so it must be a DOM element or a `forwardRef` component (the toolbar passes its `ToolbarButton`). |
+| `labels` | `Partial<LinkPopoverLabels>` | i18n labels (`defaultLinkPopoverLabels` is exported). |
+| `className` / `style` | `string` / `CSSProperties` | Extra class / inline style on the panel; placement stays with Radix. |
+
+Styling hooks (internals are hashed CSS-module classes): `[data-link-popover]` on the panel, `[data-link-field]` on the input, `[data-link-action="apply|open|remove"]` on the buttons, `[data-link-invalid]` on the input while the editor rejects the address. Colors come from the theme variables (`--tmr-accent`, `--tmr-toolbar-border`, `--tmr-toolbar-muted`, `--tmr-text`, `--tmr-danger`).
+
+The logic follows the official link-popover component (MIT) — ported, not vendored, so no Tailwind, no primitive design system and no extra runtime deps. It also fixes two flaws in that reference implementation, both caught by tests here: a rejected address used to leave the document modified (the insert-after-a-failed-`setLink` chain), and editing a link whose caret sits inside it replaced the link's text with the URL. What it does:
+
+- applies over `extendMarkRange('link')`, so changes hit the whole link;
+- inserts the address as its own text when the selection is empty and there is no link;
+- removes without letting the autolink plugin re-add the link (`preventAutolink`);
+- normalises bare domains and `host:port` with the extension's `defaultProtocol` (typing `example.com` stores `http://example.com`, matching what Tiptap's autolink does on paste — otherwise markdown would export a relative link);
+- opens through a protocol allowlist with `noopener,noreferrer`;
+- keeps its Enter IME-safe (the official panel's handler would apply the link while you commit a Chinese/Japanese candidate).
+
+The commands are exported for headless or self-drawn UIs: `applyLink`, `removeLink`, `canSetLink`, `isLinkActive`, `readLinkHref`, `normalizeLinkHref`, `sanitizeLinkUrl`, `openLinkUrl`.
 
 ### `<MarkdownPreview>` (client)
 

package/dist/components/EditorToolbar.d.ts

@@ -61,6 +61,17 @@ export interface EditorToolbarProps {
     /** 是否显示导入下拉，默认 `true`。卡片等场景可关掉。 */
     showImport?: boolean;
     labels?: Partial<ToolbarLabels>;
+    /**
+     * 工具栏最右端的搜索入口（放大镜）。**不传就不渲染**——条子本身归
+     * `<MarkdownWysiwygEditor>`，这里只给一个入口，宿主接上自己的编辑器句柄即可：
+     * `onSearch={() => handle.current?.openFind()}`。
+     *
+     * 条子归编辑器渲染（`findBar` 开）时才接；`findBar={false}` 的宿主自己摆条子，
+     * 这个入口点了也不会弹东西。只读态照样可查，所以不随 `editable` 灰显。
+     */
+    onSearch?: () => void;
+    /** 条子当前是否开着（驱动按钮的 aria-pressed / 高亮）。不传恒为未激活。 */
+    searchActive?: boolean;
     /** 追加到 More 菜单末尾的自定义项。 */
     extraToolbarItems?: ExtraToolbarItem[];
     className?: string;
@@ -70,4 +81,4 @@ export type { ImportMenuItem };
  * 顶部操作栏（antd-free，Radix Popover 菜单 + 内联 SVG 图标）。位置由父级控制，
  * 这里只渲染按钮 + 反映 editor 激活态。不含业务耦合，扩展项经 extraToolbarItems 注入。
  */
-export declare function EditorToolbar({ editor, onImageUpload, onError, onImportDocument, importAccept, importMenuItems, showImport, labels, extraToolbarItems, className, }: EditorToolbarProps): import("react").JSX.Element;
+export declare function EditorToolbar({ editor, onImageUpload, onError, onImportDocument, importAccept, importMenuItems, showImport, labels, onSearch, searchActive, extraToolbarItems, className, }: EditorToolbarProps): import("react").JSX.Element;

package/dist/components/EditorToolbar.dom.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/components/FindReplaceBar.d.ts

@@ -17,11 +17,4 @@ export interface FindReplaceBarProps {
     /** 根节点内联样式（编辑器用它落 findBarOffset；宿主自绘时也可用）。 */
     style?: CSSProperties;
 }
-/**
- * 查找替换浮动条。匹配、高亮、替换全部由官方
- * `@tiptap/extension-find-and-replace` 承担（含 RE2 安全正则、跨标记匹配、单事务全部替换），
- * 这里只做输入、计数、开关与键位。
- *
- * 打开即把查询推给编辑器，关闭时 `clearSearch()`——高亮是会话级的，不留残影。
- */
 export declare function FindReplaceBar({ editor, onClose, labels, inputRef, className, style, }: FindReplaceBarProps): import("react").JSX.Element | null;

package/dist/components/LinkPopover.d.ts

@@ -0,0 +1,28 @@
+import { Editor } from '@tiptap/react';
+import { CSSProperties, ReactNode } from 'react';
+import { LinkPopoverLabels } from '../labels';
+export interface LinkPopoverProps {
+    /** 编辑器实例。 */
+    editor: Editor;
+    /**
+     * 触发器：传宿主自己的按钮元素。Radix 的 `asChild` 要接管它的点击 / ref / aria——
+     * 传函数组件时得先 `forwardRef`（本库的 `<EditorToolbar>` 就是这么接的）。
+     */
+    trigger: ReactNode;
+    labels?: Partial<LinkPopoverLabels>;
+    /** 挂到浮层根节点上的 class / 内联样式（定位与层级归宿主，Radix 只管浮层方向）。 */
+    className?: string;
+    style?: CSSProperties;
+}
+/**
+ * 链接编辑浮层：输入地址 + 应用 / 在新窗口打开 / 移除。
+ *
+ * 逻辑全在 `linkEditing.ts`（从官方 UI Components 的 `useLinkPopover` 搬的），这里只负责输入、
+ * 按钮与状态。取代表驱动器的 `window.prompt`：能**编辑已有链接**（打开即预填当前地址，
+ * 而旧实现是「在链接里点一下就删除」）、能打开、能移除，且 `window.prompt` 在 Electron /
+ * 部分 WebView 里根本不可用。
+ *
+ * 地址被编辑器拒掉时（Tiptap 的 `isAllowedUri`）浮层不关，输入框转成危险色并带上 title，
+ * 让用户改——静默什么都不发生是最难查的。
+ */
+export declare function LinkPopover({ editor, trigger, labels, className, style, }: LinkPopoverProps): import("react").JSX.Element;

package/dist/components/LinkPopover.dom.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/components/MarkdownWysiwygEditor.d.ts

@@ -32,6 +32,11 @@ export interface MarkdownWysiwygEditorHandle {
     openFind: () => void;
     /** 收起自带浮动条，清空高亮并把焦点还给编辑器。findBar={false} 时不生效。 */
     closeFind: () => void;
+    /**
+     * 反转自带浮动条：关着就开、开着就关。工具栏那个带 active 态的放大镜接它
+     * （`onSearch={() => handle.current?.toggleFind()}`）。findBar={false} 时不生效。
+     */
+    toggleFind: () => void;
 }
 export interface MarkdownWysiwygEditorProps {
     /** 初始 markdown 内容。 */
@@ -145,6 +150,13 @@ export interface MarkdownWysiwygEditorProps {
     findShortcut?: boolean;
     /** 查找替换浮动条的本地化文案。 */
     findLabels?: Partial<FindLabels>;
+    /**
+     * 浮动条开合状态变化的通知（条子开着时 `handle.openFind()`、Esc / × 关掉都会触发）。
+     * 典型用法是驱动别处的入口按钮：`<EditorToolbar onSearch={open} searchActive={isOpen} />`。
+     * 只在真正变化时回调，挂载时不会先报一次 `false`；报的是「条子真的在屏幕上」——
+     * `findBar={false}`（宿主自己摆条子）时恒为 `false`，不会因为 `openFind()` 空转就亮起入口。
+     */
+    onFindOpenChange?: (open: boolean) => void;
     /**
      * 启用快捷键抽屉：编辑器右下角出现键盘悬浮按钮，点开为
      * 「格式 / 快捷键 / Markdown」三列对照抽屉（默认 true，只读态隐藏）。

package/dist/components/TableHandles.d.ts

@@ -0,0 +1,19 @@
+import { Editor } from '@tiptap/core';
+import { ToolbarLabels } from '../labels';
+export interface TableHandlesProps {
+    /** 编辑器实例。只读态不出手柄。 */
+    editor: Editor;
+    /** 已合并默认值的工具栏文案（行列菜单项与两个手柄的 aria-label 都取自它）。 */
+    labels: ToolbarLabels;
+}
+/**
+ * 表格的悬停手柄（Notion 式）：鼠标落在单元格上时，行左缘出一条竖胶囊（⋮）、表格上方出一条
+ * 横胶囊（⋯），点开就是该行 / 该列的操作菜单。
+ *
+ * 这是原来「表内右键出菜单」的替代——右键只保留**多格选区**的批量增删（手柄只覆盖单行单列，
+ * 那个场景手柄表达不了）。命令全部复用 `tableSelection.ts`，与工具栏的「插入表格」共用一套。
+ *
+ * 手柄是 fixed 定位、渲染在 body 的 portal 里：它要贴着单元格边缘，而工具栏并不在编辑器 DOM
+ * 内。滚动 / 缩放时重新量一遍悬停的那颗单元格，让手柄跟着走。
+ */
+export declare function TableHandles({ editor, labels }: TableHandlesProps): import('react').ReactPortal | null;

package/dist/components/TableHandles.dom.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/components/findEntry.dom.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/findReplace.d.ts

@@ -1,10 +1,24 @@
+import { Editor } from '@tiptap/react';
+/** 官方扩展在 `extensionManager` 里的注册名（与官方 UI Components 同款判据）。 */
+export declare const FIND_EXTENSION_NAME = "findAndReplace";
 /**
- * 查找替换的适配层。
+ * 输入法组合中的这次按键要不要放行。
  *
- * 匹配 / 高亮 / 替换全部由官方 `@tiptap/extension-find-and-replace` 承担（命令 + storage +
- * decoration），宿主与 AI 侧可以直接用 `editor.commands.setSearchTerm / replaceAll …`。
- * 这个文件只收拾 Tiptap 3.31.3 上的一个坑，以及库内的默认防抖。
+ * 中文 / 日文输入法里 Enter 是「提交候选词」、Escape 是「取消候选」，都不是「执行」：不拦的话，
+ * 每次确认候选词都会触发一次跳转（替换框则直接替换一处），而按 Esc 想取消候选反而把浮动条关掉。
+ * 判据取两路——`isComposing` 覆盖常规路径，`keyCode === 229` 兜住 Safari 在组合收尾时的 keydown
+ * （与 slashMenu/SlashMenuExtension.ts 的 isComposing() 同一套；那边还多一路 ProseMirror 的
+ * `view.composing`，React 事件里拿不到，调用方传 `event.nativeEvent` 即可）。
  */
+export declare function isComposingKeyEvent(event: Pick<KeyboardEvent, 'isComposing' | 'keyCode'>): boolean;
+/**
+ * 查找替换扩展是否已注册。
+ *
+ * 按 `extensionManager.extensions` 里的注册名查，而不是探 `editor.commands.setSearchTerm`
+ * 在不在——命令探测分不清「扩展根本没装」和「命令被别的同名扩展覆盖」，也判不出已销毁的实例。
+ * 官方 UI Components 的 `isFindAndReplaceAvailable` 用的是同一条判据。
+ */
+export declare function hasFindReplaceExtension(editor: Editor | null | undefined): boolean;
 /**
  * 输入防抖（毫秒）。
  *

package/dist/icons/index.d.ts

@@ -16,6 +16,12 @@ export declare const UnderlineIcon: (p: IconProps) => import("react").JSX.Elemen
 export declare const StrikethroughIcon: (p: IconProps) => import("react").JSX.Element;
 export declare const CodeIcon: (p: IconProps) => import("react").JSX.Element;
 export declare const LinkIcon: (p: IconProps) => import("react").JSX.Element;
+/** 橡皮擦：表格菜单的「清空内容」。 */
+export declare const EraserIcon: (p: IconProps) => import("react").JSX.Element;
+/** 逆时针回转：表格菜单的「重置单元格样式」。 */
+export declare const RotateCcwIcon: (p: IconProps) => import("react").JSX.Element;
+/** 在新窗口打开（链接浮层的「打开」按钮）。 */
+export declare const ExternalLinkIcon: (p: IconProps) => import("react").JSX.Element;
 export declare const ImageIcon: (p: IconProps) => import("react").JSX.Element;
 export declare const ImportIcon: (p: IconProps) => import("react").JSX.Element;
 export declare const ListUnorderedIcon: (p: IconProps) => import("react").JSX.Element;

package/dist/index.d.ts

@@ -5,6 +5,8 @@ export { ColorPalette, type ColorPaletteProps } from './components/ColorPalette'
 export { TocPanel, type TocPanelProps } from './components/TocPanel';
 export { CodeBlockView } from './components/CodeBlockView';
 export { FindReplaceBar, type FindReplaceBarProps, } from './components/FindReplaceBar';
+export { LinkPopover, type LinkPopoverProps } from './components/LinkPopover';
+export { applyLink, canSetLink, isLinkActive, normalizeLinkHref, openLinkUrl, readLinkHref, removeLink, sanitizeLinkUrl, } from './linkEditing';
 export { ReportContent, type ReportContentProps } from './ReportContent';
 export { CitationInteractive, type CitationInteractiveProps, } from './components/CitationInteractive';
 export { ReportContentInteractive, type ReportContentInteractiveProps, } from './components/ReportContentInteractive';
@@ -27,7 +29,7 @@ export { MarkdownFileDrop } from './markdownFileDrop';
 export { extractToc, type TocItem } from './toc/extractToc';
 export { makeTocGetId } from './toc/tocSlug';
 export { scrollToTocHeading } from './toc/scrollToTocHeading';
-export { defaultChartLabels, defaultCodeBlockLabels, defaultColorPaletteLabels, defaultCommentLabels, defaultFindLabels, defaultShortcutLabels, defaultSlashMenuLabels, defaultTocLabels, defaultToolbarLabels, type ChartLabels, type CodeBlockLabels, type ColorPaletteLabels, type CommentLabels, type FindLabels, type ShortcutLabels, type SlashMenuLabels, type TocLabels, type ToolbarLabels, } from './labels';
+export { defaultChartLabels, defaultCodeBlockLabels, defaultColorPaletteLabels, defaultCommentLabels, defaultFindLabels, defaultLinkPopoverLabels, defaultShortcutLabels, defaultSlashMenuLabels, defaultTocLabels, defaultToolbarLabels, type ChartLabels, type CodeBlockLabels, type ColorPaletteLabels, type CommentLabels, type FindLabels, type LinkPopoverLabels, type ShortcutLabels, type SlashMenuLabels, type TocLabels, type ToolbarLabels, } from './labels';
 export { CommentMark, type CommentMarkOptions, type CommentInterval } from './commentAnchor/CommentMark';
 export { mapCommentAnchors, mergeCommentIntervals, blockTextHash, type CommentSegment, type CommentAnchorInput, type CommentAnchorResult, type CommentAnchorStatus, type CommentRange, } from './commentAnchor/commentMapper';
 export { commentAnchorPlugin, commentAnchorExtension, commentAnchorPluginKey, stripCommentAnchorMarks, COMMENT_ACTIVE_META, COMMENT_CLICK_META, COMMENT_GUTTER_META, type CommentAnchorPluginOptions, type CommentAnchorPluginState, type CommentGutterPayload, } from './commentAnchor/commentAnchorPlugin';