@stacksjs/ts-cloud 0.7.120 → 0.7.121

package/dist/deploy/release-content.d.ts

@@ -0,0 +1,37 @@
+/**
+ * Pre-flight check on what a site is about to ship.
+ *
+ * `existsSync(site.root)` was the only gate before this, and a directory
+ * existing says nothing about whether it holds a servable site. The failure it
+ * missed is specific and expensive: a static-site generator that renders into a
+ * SUBDIRECTORY of its output directory (BunPress writes `<outdir>/.bunpress`,
+ * and it is far from alone) leaves the configured `root` existing but holding
+ * only that one child. The tarball then ships `current/.bunpress/index.html`,
+ * the gateway serves `current/`, and every URL 404s while the deploy prints
+ * success and exits 0.
+ *
+ * So the check looks at the content, and when the content says the root is one
+ * level too high it says so by name instead of leaving it to be found in
+ * production.
+ */
+export interface ReleaseContentIssue {
+    level: 'error' | 'warning';
+    message: string;
+}
+export interface CheckReleaseContentOptions {
+    /** The site's resolved `root`, as configured. */
+    root: string;
+    /** Site key, for messages. */
+    siteName: string;
+    /**
+     * Static sites are served by path from the release root, so a missing
+     * top-level `index.html` means the domain root 404s. An app site ships a
+     * source tree and has no such expectation.
+     */
+    expectIndex: boolean;
+}
+/**
+ * Inspect what a site is about to package. Returns every issue found; the
+ * caller fails the deploy when any of them is an `error`.
+ */
+export declare function checkReleaseContent(options: CheckReleaseContentOptions): ReleaseContentIssue[];

package/dist/deploy/release-content.test.d.ts

@@ -0,0 +1 @@
+export {};