@lotics/ui 12.1.0 → 12.1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/ui",
-  "version": "12.1.0",
+  "version": "12.1.1",
   "type": "module",
   "exports": {
     "./vite": {

package/src/remark_gfm_safe.ts

@@ -6,6 +6,29 @@ import { gfmTaskListItemFromMarkdown } from "mdast-util-gfm-task-list-item";
 import { gfm } from "micromark-extension-gfm";
 import type { Plugin } from "unified";
 
+// A micromark syntax extension is exactly what `gfm()` produces; deriving the type
+// from the imported value keeps this dependency-free (`micromark-util-types` is
+// only a transitive dep) while staying the true type the registry holds.
+type MicromarkExtension = ReturnType<typeof gfm>;
+
+// `unified`'s `Data` interface ships bare (`{ settings? }`). `remark-parse` is what
+// normally augments it with the two extension registries a `fromMarkdown` plugin
+// writes into via `this.data()` — but this module composes GFM from its parts
+// precisely so it never imports the `remark-gfm`/autolink-literal graph, and it
+// doesn't import `remark-parse` either, so nothing else in a consumer's compile
+// graph declares them. We restate the ecosystem's canonical augmentation here so
+// the writes below type-check for every app that pulls this file in through
+// `<Markdown>` (without it, `tsc` throws TS2339 on the whole app). Types mirror
+// the consumers: `micromarkExtensions` holds micromark `Extension`s;
+// `fromMarkdownExtensions` mirrors `mdast-util-from-markdown`'s `mdastExtensions`
+// shape (`Extension | Extension[]`), which is what we push a nested list into below.
+declare module "unified" {
+  interface Data {
+    micromarkExtensions?: MicromarkExtension[];
+    fromMarkdownExtensions?: Array<Extension | Extension[]>;
+  }
+}
+
 /**
  * `remark-gfm`, rebuilt so no regex lookbehind reaches the bundle.
  *