blume 0.3.0 → 0.5.0

package/dist/types/core/data.d.ts

@@ -87,6 +87,8 @@ export interface BlumeDataConfig {
     favicon: BlumeFavicon;
     feedback: boolean;
     i18n: BlumeDataI18n | null;
+    /** Default icon library for bare `icon` names. */
+    icons: ResolvedConfig["icons"];
     /** `markdown.imageZoom`: click-to-zoom content images. */
     imageZoom: boolean;
     logo: BlumeLogo | null;

package/dist/types/core/project.d.ts

@@ -2,8 +2,18 @@ import type { ResolvedConfig } from "./schema.ts";
 import type { ProjectContext } from "./types.ts";
 /** Locate the Blume config file for a project root, if any. */
 export declare const findConfigFile: (root: string) => string | null;
+/**
+ * Resolve the generated runtime directory for a project. Defaults to
+ * `<root>/.blume`; an override (e.g. `.blume-verify` for an isolated build that
+ * runs alongside a live `blume dev`) may be relative to the root or absolute.
+ */
+export declare const resolveRuntimeDir: (root: string, runtimeDir?: string) => string;
 /**
  * Resolve every path Blume needs from a project root and its resolved config.
- * Paths are absolute and normalized.
+ * Paths are absolute and normalized. `options.runtimeDir` relocates the whole
+ * generated runtime (and its build output) so a verify build/check can run
+ * without touching a live dev server's `.blume/` or the real `dist/`.
  */
-export declare const resolveProjectContext: (root: string, config: ResolvedConfig) => ProjectContext;
+export declare const resolveProjectContext: (root: string, config: ResolvedConfig, options?: {
+    runtimeDir?: string;
+}) => ProjectContext;