blume 0.1.2 → 0.1.3

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

@@ -1458,11 +1458,17 @@ export declare const blumeConfigSchema: z.ZodObject<{
     }>>;
     description: z.ZodOptional<z.ZodString>;
     /**
-     * Directory (relative to the project root) that `<Component path>` resolves
-     * live previews and their source against. Defaults to `examples`; point it
-     * elsewhere when examples live outside a top-level `examples/` — e.g. a
-     * registry layout like `registry/<pkg>`, where a `<Component path>` key is
-     * then relative to that directory.
+     * Where `<Component path>` resolves live previews and their source from,
+     * relative to the project root. Defaults to the `examples` directory; point
+     * it elsewhere when examples live outside a top-level `examples/`.
+     *
+     * May be a glob (anything with `*`/`?`/`[]`/`{}`/`!`), in which case only
+     * matching files are discovered and a `<Component path>` key is relative to
+     * the glob's static prefix. Use this for a registry layout that colocates
+     * component sources with their examples — `registry/<pkg>/**\/examples/*`
+     * targets just the examples, leaving the sources (which have no default
+     * export to wrap) out, so the registry needn't be forked into its own
+     * examples directory.
      */
     examples: z.ZodDefault<z.ZodString>;
     export: z.ZodDefault<z.ZodEffects<z.ZodUnion<[z.ZodBoolean, z.ZodObject<{

package/docs/content/components.mdx

@@ -589,6 +589,26 @@ export default defineConfig({
 <Component path="file-list/basic" />
 ```
 
+`examples` can also be a glob (anything with `*`, `?`, `[]`, `{}`, or `!`). Only
+matching files are discovered, and `path` is relative to the glob's static prefix
+(the part before the first wildcard). This is for a registry that colocates each
+component's source with its example — point at just the examples so the sources,
+which have no default export to preview, aren't swept in:
+
+```ts
+// blume.config.ts
+export default defineConfig({
+  // registry/files-sdk/file-list/file-list.tsx — source, left out
+  // registry/files-sdk/file-list/examples/basic.tsx — discovered
+  examples: "registry/files-sdk/**/examples/*",
+});
+```
+
+```astro
+<!-- keyed relative to registry/files-sdk -->
+<Component path="file-list/examples/basic" />
+```
+
 <Component path="counter" />
 
 ```astro

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "blume",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Documentation that's fast, AI-ready, and zero-config.",
   "keywords": [
     "astro",

package/src/astro/examples.ts

@@ -40,25 +40,62 @@ const FRAMEWORK_BY_EXT: Record<string, ExampleFramework> = {
 };
 
 // Captures the extension so we can strip it from the path key and pick the
-// framework. Kept in sync with the glob below.
+// framework. Kept in sync with the glob below — non-matching files a user glob
+// happens to sweep in (e.g. a registry's `.ts` sources) are dropped here.
 const EXAMPLE_FILE = /\.(?<ext>astro|jsx|svelte|tsx|vue)$/u;
 
+// Renderable example files when `examples` names a plain directory.
+const DEFAULT_EXAMPLE_GLOB = "**/*.{astro,jsx,svelte,tsx,vue}";
+
+// Glob magic that turns `examples` from a plain directory into a pattern. `()`,
+// `@`, and `+` are excluded so literal path segments (npm scopes, parens) keep
+// resolving as directories; the extglob leads `*?!` still trigger here.
+const GLOB_MAGIC = /[!*?[\]{}]/u;
+
+/**
+ * Split a glob into its static directory prefix and the remaining pattern, so
+ * discovered files can be keyed relative to that prefix (e.g.
+ * `registry/x/**\/examples/*` → `{ base: "registry/x", rest: "**\/examples/*" }`).
+ */
+const splitGlobBase = (pattern: string): { base: string; rest: string } => {
+  const segments = pattern.split("/");
+  const firstMagic = segments.findIndex((segment) => GLOB_MAGIC.test(segment));
+  if (firstMagic === -1) {
+    return { base: pattern, rest: "" };
+  }
+  return {
+    base: segments.slice(0, firstMagic).join("/"),
+    rest: segments.slice(firstMagic).join("/"),
+  };
+};
+
 /**
- * Discover preview examples under `<root>/<subdir>` (the `examples` config,
- * default `examples`). Every `.astro`/`.tsx`/`.jsx`/`.vue`/`.svelte` file
- * becomes addressable by `<Component path="...">`, where the path is the file's
- * location under that directory without its extension (e.g. `forms/login.tsx` →
- * `forms/login`). Discovery is path-based (a glob), so no example code is
- * executed. Framework examples carry a hydration mode (default `client:visible`,
- * overridable via `export const client`); `.astro` examples render statically
- * with no client directive.
+ * Discover preview examples for the `examples` config (default `examples`).
+ * Every `.astro`/`.tsx`/`.jsx`/`.vue`/`.svelte` file becomes addressable by
+ * `<Component path="...">`, where the path is the file's location without its
+ * extension (e.g. `forms/login.tsx` → `forms/login`).
+ *
+ * `pattern` is a directory by default, but may be a glob (anything with
+ * `*`/`?`/`[]`/`{}`/`!`) — then only matching files are discovered and each
+ * `<Component path>` key is relative to the glob's static prefix. This lets a
+ * registry layout that colocates component sources with their examples be
+ * targeted directly (e.g. `registry/<pkg>/**\/examples/*`) without the sources —
+ * which have no default export and so can't be wrapped — being swept in.
+ *
+ * Discovery is path-based (a glob), so no example code is executed. Framework
+ * examples carry a hydration mode (default `client:visible`, overridable via
+ * `export const client`); `.astro` examples render statically with no client
+ * directive.
  */
 export const discoverExamples = async (
   root: string,
-  subdir = "examples"
+  pattern = "examples"
 ): Promise<ExampleDiscovery> => {
-  const dir = join(root, subdir);
-  const matches = await glob(["**/*.{astro,jsx,svelte,tsx,vue}"], {
+  const { base, rest } = GLOB_MAGIC.test(pattern)
+    ? splitGlobBase(pattern)
+    : { base: pattern, rest: DEFAULT_EXAMPLE_GLOB };
+  const dir = join(root, base);
+  const matches = await glob([rest], {
     absolute: true,
     cwd: dir,
     onlyFiles: true,

package/src/astro/generate.ts

@@ -1054,10 +1054,19 @@ export const generateRuntime = async (
     ...exampleDiscovery.warnings,
   ];
 
-  // The new provider SDKs are optional peers; warn (rather than fail opaquely in
-  // Vite) when the configured provider's package isn't installed.
+  // Provider SDKs are optional peers; warn (rather than fail opaquely in Vite)
+  // when the configured provider's package isn't installed. A dep is available
+  // if the project installed it (resolves from the root) OR Blume ships it
+  // (resolves from the Blume package — the same set the `.blume` deps link
+  // exposes to the build). Resolving from the project root alone falsely flagged
+  // a shipped SDK like Orama (the default provider) as missing whenever it
+  // wasn't hoisted into the project, e.g. under isolated linkers. We resolve
+  // from each package's real location rather than through the `.blume` junction,
+  // which can't be traversed reliably for store-symlinked deps.
   for (const dep of searchProviderMeta(config.search.provider).runtimeDeps) {
-    if (!canResolveFrom(context.root, dep)) {
+    if (
+      !(canResolveFrom(context.root, dep) || canResolveFrom(packageRoot(), dep))
+    ) {
       warnings.push(
         `Search provider "${config.search.provider}" needs "${dep}", which isn't installed. Run \`npm install ${dep}\` (or your package manager's equivalent).`
       );

package/src/core/schema.ts

@@ -1022,11 +1022,17 @@ export const blumeConfigSchema = z
     deployment: deploymentConfigSchema.default({}),
     description: z.string().optional(),
     /**
-     * Directory (relative to the project root) that `<Component path>` resolves
-     * live previews and their source against. Defaults to `examples`; point it
-     * elsewhere when examples live outside a top-level `examples/` — e.g. a
-     * registry layout like `registry/<pkg>`, where a `<Component path>` key is
-     * then relative to that directory.
+     * Where `<Component path>` resolves live previews and their source from,
+     * relative to the project root. Defaults to the `examples` directory; point
+     * it elsewhere when examples live outside a top-level `examples/`.
+     *
+     * May be a glob (anything with `*`/`?`/`[]`/`{}`/`!`), in which case only
+     * matching files are discovered and a `<Component path>` key is relative to
+     * the glob's static prefix. Use this for a registry layout that colocates
+     * component sources with their examples — `registry/<pkg>/**\/examples/*`
+     * targets just the examples, leaving the sources (which have no default
+     * export to wrap) out, so the registry needn't be forked into its own
+     * examples directory.
      */
     examples: z.string().default("examples"),
     export: exportConfigSchema.default(false),

package/src/registry/eject.ts

@@ -73,7 +73,7 @@ export const eject = async (root: string): Promise<string[]> => {
         : Promise.resolve(""),
       buildRawMarkdown(project),
       discoverIslands(root),
-      discoverExamples(root),
+      discoverExamples(root, config.examples),
     ]);
   // Island/example frameworks drive which Astro renderers the ejected config
   // wires in; React also switches on for project `.tsx`/`.jsx` and Ask AI.