@clarify-labs/cli 0.11.3 → 0.11.4

package/output/index.cjs

@@ -1,5 +1,5 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-const require_engine = require("./engine-6WmOk7xk.cjs");
+const require_engine = require("./engine-Cgc71w13.cjs");
 exports.ClarifyEngine = require_engine.ClarifyEngine;
 exports.createClarifyEngine = require_engine.createClarifyEngine;
 exports.createViteAdapter = require_engine.createViteAdapter;

package/output/index.js

@@ -1,2 +1,2 @@
-import { l as createViteAdapter, n as createClarifyEngine, t as ClarifyEngine, u as defineConfig } from "./engine-CrYRJRZT.js";
+import { l as createViteAdapter, n as createClarifyEngine, t as ClarifyEngine, u as defineConfig } from "./engine-CJmXVTo5.js";
 export { ClarifyEngine, createClarifyEngine, createViteAdapter, defineConfig };

package/output/parsers/markdown/markdown.d.ts

@@ -0,0 +1,34 @@
+import { ContentDiagnostic } from '../../types.js';
+type CompileMarkdownContentOptions = {
+    filePath?: string;
+    projectRoot?: string;
+};
+/**
+ * Validate Markdown content for diagnostics WITHOUT running the build-time
+ * rehype pipeline (Shiki highlighting, slug injection, code-block parsing).
+ *
+ * `rehypePlugins` includes `rehypeShiki`, which loads grammar/WASM assets and
+ * is expensive. The real highlighting happens at Vite build time via the
+ * `@mdx-js/rollup` plugin (see `createContentCompilerPlugin` in
+ * `core/adapters.ts`), which runs the full remark + rehype pipeline.
+ * Re-running it here, during route discovery (Phase 3), would compile every
+ * `.md` file twice and invoke Shiki once per file per `engine.refresh()` -
+ * see ARCHITECTURE.md §2.2 which states "不应在 core 中执行代码高亮".
+ *
+ * `format: 'md'` mirrors the adapter's markdown compiler semantics (no JSX,
+ * raw HTML allowed via `remarkRehypeOptions`), so the same class of syntax
+ * errors that would break the Vite build is surfaced as a diagnostic here
+ * instead of leaking out as an opaque
+ * `Failed to fetch dynamically imported module` at runtime.
+ *
+ * MDX files are handled by `compileMdxContent` in `mdx.ts`. Keep the two
+ * compilers separate so each format can evolve its own diagnostic rules
+ * without contaminating the other.
+ */
+export declare function compileMarkdownContent(content: string, options?: CompileMarkdownContentOptions): Promise<{
+    ok: true;
+} | {
+    ok: false;
+    diagnostic: ContentDiagnostic;
+}>;
+export {};

package/output/parsers/markdown/mdx.d.ts

@@ -18,25 +18,33 @@ type ContentCompileDiagnosticOptions = {
     projectRoot?: string;
 };
 export declare function createContentCompileDiagnostic(options: ContentCompileDiagnosticOptions): ContentDiagnostic;
+type CompileContentOptions = {
+    filePath?: string;
+    projectRoot?: string;
+};
 /**
  * Validate MDX content for diagnostics WITHOUT running the build-time rehype
  * pipeline (Shiki highlighting, slug injection, code-block parsing).
  *
  * `rehypePlugins` includes `rehypeShiki`, which loads grammar/WASM assets and
  * is expensive. The real highlighting happens at Vite build time via the
- * `@mdx-js/rollup` plugins (see `createMarkdownPlugin` and `createMdxPlugin`
- * in `core/adapters.ts`), which
- * runs the full remark + rehype pipeline. Re-running it here, during route
- * discovery (Phase 3), would compile every `.mdx` file twice and invoke Shiki
- * once per file per `engine.refresh()` — see ARCHITECTURE.md §2.2 which states
- * "不应在 core 中执行代码高亮".
+ * `@mdx-js/rollup` plugin (see `createContentCompilerPlugin` in
+ * `core/adapters.ts`), which runs the full remark + rehype pipeline.
+ * Re-running it here, during route discovery (Phase 3), would compile every
+ * `.mdx` file twice and invoke Shiki once per file per `engine.refresh()` -
+ * see ARCHITECTURE.md §2.2 which states "不应在 core 中执行代码高亮".
  *
  * The remark pipeline still runs (shared with the Vite plugin via
- * `remarkPlugins`), so MDX/JSX syntax errors — the only class of error this
- * diagnostic is meant to surface ahead of the Vite build — are caught. The
+ * `remarkPlugins`), so MDX/JSX syntax errors - the only class of error this
+ * diagnostic is meant to surface ahead of the Vite build - are caught. The
  * output is discarded; only the thrown error is used.
+ *
+ * `.md` files are handled by `compileMarkdownContent` in `markdown.ts`, which
+ * mirrors the adapter's markdown compiler semantics (`format: 'md'`, raw HTML
+ * allowed). Keep the two compilers separate so each format can evolve its own
+ * diagnostic rules without contaminating the other.
  */
-export declare function compileMdxContent(content: string, filePath?: string, projectRoot?: string): Promise<{
+export declare function compileMdxContent(content: string, options?: CompileContentOptions): Promise<{
     ok: true;
 } | {
     ok: false;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clarify-labs/cli",
-  "version": "0.11.3",
+  "version": "0.11.4",
   "license": "AGPL-3.0-only",
   "type": "module",
   "repository": {
@@ -39,8 +39,8 @@
   },
   "dependencies": {
     "@apidevtools/swagger-parser": "^12.1.0",
-    "@clarify-labs/renderer": "0.11.3",
-    "@clarify-labs/templates": "0.11.3",
+    "@clarify-labs/renderer": "0.11.4",
+    "@clarify-labs/templates": "0.11.4",
     "@mdx-js/mdx": "^3.1.1",
     "@mdx-js/rollup": "^3.1.1",
     "@modelcontextprotocol/sdk": "^1.29.0",