canopycms 0.0.62 → 0.0.64

package/dist/build-canopy.d.ts

@@ -0,0 +1,48 @@
+import type { CanopyConfig } from './config/index.js';
+import type { EntrySchemaRegistry } from './schema/types.js';
+import { type CanopyBuildContext } from './context.js';
+export interface CreateBuildCanopyOptions {
+    /**
+     * Entry schema registry for resolving `.collection.json` references.
+     * Same shape as `createCanopyServices`'s option of the same name.
+     */
+    entrySchemaRegistry?: EntrySchemaRegistry;
+}
+/**
+ * One-call factory for a **build/admin** Canopy context — for standalone
+ * scripts that run entirely outside a Next.js request or build phase (index
+ * builders, content audits, codegen, ad hoc reports).
+ *
+ * **This is a build/admin context: it reads the filesystem directly as a
+ * synthetic admin user (`STATIC_DEPLOY_USER`) and bypasses ALL branch and
+ * path ACLs.** There is no per-request auth to enforce because there is no
+ * request. Do not reach for this from request-handling code (an API route,
+ * a server component rendering for a specific visitor, anything with a real
+ * user on the other end) — there, use `createNextCanopyContext(...)`'s
+ * `getCanopy()` (or its phase-selecting `read`/`readByUrlPath`), which
+ * enforce branch/path permissions per user. This factory mirrors the same
+ * `createCanopyServices` + `createCanopyContext` + `STATIC_DEPLOY_USER` boot
+ * sequence that `createNextCanopyContext`'s own `getCanopyForBuild()` uses
+ * internally, minus the Next.js pieces (no `next/headers`, no React
+ * `cache()`, no request-time misuse guard — there is no request phase for
+ * it to guard against) — so it works in a plain script run with `tsx`/`node`.
+ *
+ * Trivially stubbable by design: the boot sequence is one function call
+ * taking a plain config object and returning a plain context, so a script
+ * that calls it can be imported and exercised from a test with the config
+ * (or this function itself) swapped out. Contrast with a hand-rolled
+ * top-level-`await` boot block, which can never be imported by a test at
+ * all — that's the concrete problem this factory removes.
+ *
+ * @example
+ * ```ts
+ * // scripts/build-search-index.ts
+ * import { createBuildCanopy } from 'canopycms/server'
+ * import config from '../canopycms.config.js'
+ * import { entrySchemaRegistry } from '../src/schemas.js'
+ *
+ * const canopy = await createBuildCanopy(config.server, { entrySchemaRegistry })
+ * const entries = await canopy.listEntries()
+ * ```
+ */
+export declare function createBuildCanopy(config: CanopyConfig, options?: CreateBuildCanopyOptions): Promise<CanopyBuildContext>;

package/dist/build-canopy.js

@@ -0,0 +1,50 @@
+import { createCanopyServices } from './services.js';
+import { createCanopyContext } from './context.js';
+import { STATIC_DEPLOY_USER } from './build-mode.js';
+/**
+ * One-call factory for a **build/admin** Canopy context — for standalone
+ * scripts that run entirely outside a Next.js request or build phase (index
+ * builders, content audits, codegen, ad hoc reports).
+ *
+ * **This is a build/admin context: it reads the filesystem directly as a
+ * synthetic admin user (`STATIC_DEPLOY_USER`) and bypasses ALL branch and
+ * path ACLs.** There is no per-request auth to enforce because there is no
+ * request. Do not reach for this from request-handling code (an API route,
+ * a server component rendering for a specific visitor, anything with a real
+ * user on the other end) — there, use `createNextCanopyContext(...)`'s
+ * `getCanopy()` (or its phase-selecting `read`/`readByUrlPath`), which
+ * enforce branch/path permissions per user. This factory mirrors the same
+ * `createCanopyServices` + `createCanopyContext` + `STATIC_DEPLOY_USER` boot
+ * sequence that `createNextCanopyContext`'s own `getCanopyForBuild()` uses
+ * internally, minus the Next.js pieces (no `next/headers`, no React
+ * `cache()`, no request-time misuse guard — there is no request phase for
+ * it to guard against) — so it works in a plain script run with `tsx`/`node`.
+ *
+ * Trivially stubbable by design: the boot sequence is one function call
+ * taking a plain config object and returning a plain context, so a script
+ * that calls it can be imported and exercised from a test with the config
+ * (or this function itself) swapped out. Contrast with a hand-rolled
+ * top-level-`await` boot block, which can never be imported by a test at
+ * all — that's the concrete problem this factory removes.
+ *
+ * @example
+ * ```ts
+ * // scripts/build-search-index.ts
+ * import { createBuildCanopy } from 'canopycms/server'
+ * import config from '../canopycms.config.js'
+ * import { entrySchemaRegistry } from '../src/schemas.js'
+ *
+ * const canopy = await createBuildCanopy(config.server, { entrySchemaRegistry })
+ * const entries = await canopy.listEntries()
+ * ```
+ */
+export async function createBuildCanopy(config, options = {}) {
+    const services = await createCanopyServices(config, {
+        entrySchemaRegistry: options.entrySchemaRegistry,
+    });
+    const { buildContentTree, listEntries, read, readByUrlPath, services: contextServices, } = await createCanopyContext({
+        services,
+        extractUser: async () => STATIC_DEPLOY_USER,
+    }).getContext();
+    return { buildContentTree, listEntries, read, readByUrlPath, services: contextServices };
+}

package/dist/build-mode.d.ts

@@ -1,4 +1,4 @@
-import type { AuthenticatedUser } from './user';
+import type { AuthenticatedUser } from './user.js';
 /**
  * Check if this deployment is static (no request context, no auth).
  * When true: STATIC_DEPLOY_USER is used, permissions are skipped.
@@ -19,4 +19,3 @@ export declare const isBuildMode: () => boolean;
  * Has Admin privileges — all content is readable, permissions are skipped.
  */
 export declare const STATIC_DEPLOY_USER: AuthenticatedUser;
-//# sourceMappingURL=build-mode.d.ts.map

package/dist/build-mode.js

@@ -32,4 +32,3 @@ export const STATIC_DEPLOY_USER = Object.freeze({
     email: 'static-deploy@canopycms',
     name: 'Static Deploy',
 });
-//# sourceMappingURL=build-mode.js.map

package/dist/cli/cli.d.ts

@@ -9,7 +9,7 @@
  * and are dynamically imported to keep startup fast.
  */
 import minimist from 'minimist';
-import type { AuthProvider } from './init';
+import type { AuthProvider } from './init.js';
 /** Parse raw CLI args into structured flags and positional command. Exported for testing. */
 export declare function parseArgs(rawArgs: string[]): {
     argv: minimist.ParsedArgs;
@@ -40,4 +40,3 @@ type SyncSubcommand = (typeof SYNC_SUBCOMMANDS)[number];
 /** Resolve sync subcommand from positional arg. Returns null if missing or invalid. Exported for testing. */
 export declare function resolveSyncSubcommand(sub: string | undefined): SyncSubcommand | null;
 export {};
-//# sourceMappingURL=cli.d.ts.map