@tideworthy/tidysites-platform 0.1.6 → 0.1.7

package/CHANGELOG.md

@@ -1,8 +1,12 @@
 # Changelog
 
-## 0.1.3
+## 0.1.7
 
-- Renamed to `@tideworthy/tidysites-platform`: the npm scope is the parent brand, the package name says which product it serves. First version actually published to npm. No code changes.
+- Bootstrap applies the seed with the site's configured storage, so `$media` references in a template seed are downloaded into the site's media library. Before this every seed photo was skipped with "no storage configured". The storage comes from EmDash's `virtual:emdash/config` and `virtual:emdash/storage` modules, the same way the setup wizard builds it.
+
+## 0.1.6
+
+- First version on npm as `@tideworthy/tidysites-platform` (the npm scope is the parent brand; the name says which product it serves). Lockfile regenerated from a clean state so `npm ci` works on Linux runners. 0.1.3, 0.1.4, and 0.1.5 were release attempts that never reached npm; do not use them.
 
 ## 0.1.2
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@tideworthy/tidysites-platform",
-	"version": "0.1.6",
+	"version": "0.1.7",
 	"description": "The Tidysites platform integration for EmDash sites: bootstrap, sessions, maintenance, health, and publish hooks under /_tidy/*.",
 	"license": "MIT",
 	"type": "module",

package/src/lib/runtime.ts

@@ -15,15 +15,35 @@ import { createEmdashStore } from "./store";
 
 export { workerEnv } from "./env";
 
+/**
+ * The site's configured storage (R2 on Cloudflare), built the same way
+ * EmDash's setup wizard builds it: from the virtual config and storage
+ * modules the EmDash integration generates at build time. Without it,
+ * `applySeed` skips every `$media` reference in the seed.
+ */
+async function storageProvider(): Promise<unknown> {
+	try {
+		const [cfgMod, storageMod] = await Promise.all([
+			import("virtual:emdash/config") as Promise<{ default?: { storage?: { config?: unknown } } }>,
+			import("virtual:emdash/storage") as Promise<{ createStorage?: (config: unknown) => unknown }>
+		]);
+		const storageConfig = cfgMod.default?.storage;
+		if (!storageConfig || typeof storageMod.createStorage !== "function") return undefined;
+		return storageMod.createStorage(storageConfig.config);
+	} catch {
+		return undefined;
+	}
+}
+
 export async function buildDeps(): Promise<Deps> {
-	const db = await getDb();
+	const [db, storage] = await Promise.all([getDb(), storageProvider()]);
 	const store = createEmdashStore(db, { OptionsRepository, UserRepository, ulid, getMigrationStatus });
 	return {
 		store,
 		seed: {
 			load: async () => (await loadSeed()) as unknown as Record<string, unknown> & { settings?: Record<string, unknown> },
 			validate: (seed) => validateSeed(seed),
-			apply: (seed) => applySeed(db, seed as unknown as Parameters<typeof applySeed>[1], { includeContent: true, onConflict: "skip" })
+			apply: (seed) => applySeed(db, seed as unknown as Parameters<typeof applySeed>[1], { includeContent: true, onConflict: "skip", ...(storage ? { storage: storage as never } : {}) })
 		},
 		tokens: {
 			generate: () => generatePrefixedToken("ec_pat_"),

package/src/version.ts

@@ -1,3 +1,3 @@
 /** Kept in step with package.json by the release checklist in MAINTAINING.md. */
-export const VERSION = "0.1.6";
+export const VERSION = "0.1.7";
 export const PLUGIN_ID = "tidy-platform";

package/src/virtual-modules.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Virtual modules the EmDash Astro integration generates inside a site build.
+ * They exist only there; the package reaches them with dynamic imports that
+ * are wrapped in try/catch, so tests and Node never touch them.
+ */
+declare module "virtual:emdash/config" {
+	const config: { storage?: { entrypoint?: string; config?: unknown } } & Record<string, unknown>;
+	export default config;
+}
+declare module "virtual:emdash/storage" {
+	export const createStorage: ((config: unknown) => unknown) | undefined;
+}