astroidjs 0.9.3 → 0.9.5

package/dist/commerce/loader.d.ts

@@ -47,7 +47,7 @@ export declare function readCatalogItem(slug: string, options: CatalogReadOption
  *
  * ```ts
  * // src/loaders/catalog.ts
- * import { defineCatalogLoader } from "louise-toolkit/astro";
+ * import { defineCatalogLoader } from "@louise-toolkit/astro";
  * import { astroidCatalogLoaderConfig } from "astroidjs";
  *
  * export const catalogLoader = defineCatalogLoader(

package/dist/commerce/loader.js

@@ -2,7 +2,7 @@
 //
 // The catalog read, and the Live Content Collection loader over it.
 //
-// `defineCatalogLoader` (louise-toolkit/astro) already owns the Astro-facing
+// `defineCatalogLoader` (@louise-toolkit/astro) already owns the Astro-facing
 // plumbing. What each site then hand-wrote was the layer underneath — "read my
 // catalog out of D1" — and because that layer was per-site, so was the drift.
 // It doesn't need to be: once the mirror table's shape is fixed (see mirror.ts),
@@ -24,7 +24,7 @@ function decodeJson(value) {
 }
 /** Mirror row → `CatalogProduct`. */
 function toProduct(row) {
-    const { images, variants, external_id, external_slug, sort_order, synced_at, ...rest } = row;
+    const { images, variants, external_id, external_slug, sort_order, synced_at: _synced_at, ...rest } = row;
     return {
         ...rest,
         externalId: String(external_id ?? ""),
@@ -65,7 +65,7 @@ export async function readCatalogItem(slug, options) {
  *
  * ```ts
  * // src/loaders/catalog.ts
- * import { defineCatalogLoader } from "louise-toolkit/astro";
+ * import { defineCatalogLoader } from "@louise-toolkit/astro";
  * import { astroidCatalogLoaderConfig } from "astroidjs";
  *
  * export const catalogLoader = defineCatalogLoader(

package/dist/project/actions.js

@@ -4,7 +4,7 @@
 // layer 2), beside the framework-agnostic `/api/louise/*` routes.
 //
 // Astroid generated only the route half. That is not a missing convenience: the
-// two entrypoints write the SAME rows, and the whole reason `louise-toolkit/astro`
+// two entrypoints write the SAME rows, and the whole reason `@louise-toolkit/astro`
 // exposes these factories is that each one shares the raw route's store path —
 // `applyFieldSave`, `applySettingsPatch`, `applySaveDraft`. A project that wired
 // its own Actions by hand would get a second write path, and a second write path
@@ -52,7 +52,7 @@ export function generateAstroidActions(config) {
         "  louiseSaveAction,",
         "  louiseSaveDraftAction,",
         "  louiseSettingsAction,",
-        '} from "louise-toolkit/astro";',
+        '} from "@louise-toolkit/astro";',
         "import {",
         "  ASTROID_SETTINGS_COLUMNS,",
         "  ASTROID_SETTINGS_IMAGE_KEYS,",

package/dist/project/generate.js

@@ -18,7 +18,7 @@ import { ASTROID_VITALS_BINDING, astroidVitalsDataset } from "../analytics/index
 import { astroidCheckoutVars } from "../commerce/checkout-scaffold.js";
 import { astroidCommerceProviders } from "../commerce/roles.js";
 import { COMMERCE_PROVIDER_SECRETS, COMMERCE_PROVIDER_SETUP, commerceSecretNames, } from "../commerce/secrets.js";
-import { ASTROID_QUEUE_BINDING, astroidCron, astroidCrons, astroidQueueNames, astroidUsesQueues, } from "../queues/messages.js";
+import { ASTROID_QUEUE_BINDING, astroidCrons, astroidQueueNames, astroidUsesQueues, } from "../queues/messages.js";
 import { ASTROID_EDIT_SESSION_CLASS, ASTROID_REALTIME_BINDING, ASTROID_REALTIME_MIGRATION_TAG, usesRealtime, } from "../realtime/scaffold.js";
 import { ASTROID_SECRET_PLACEHOLDER } from "../secrets.js";
 import { tenancyZone } from "../tenancy/index.js";

package/dist/worker/generate.js

@@ -484,7 +484,7 @@ export function generateAstroidMiddleware(config) {
         "// the CSP header Astro's security.csp emits so Louise's data-driven inline",
         "// styles + inlined data: brand font are allowed.",
         'import { env } from "cloudflare:workers";',
-        'import { createLouiseMiddleware } from "louise-toolkit/astro";',
+        'import { createLouiseMiddleware } from "@louise-toolkit/astro";',
         // One `astroidjs` import, composed from what this config actually uses —
         // two import statements for the same module is legal and reads as an
         // oversight in a file nobody is supposed to hand-edit.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "astroidjs",
-  "version": "0.9.3",
+  "version": "0.9.5",
   "description": "Astroid — an opinionated meta-framework over Louise Toolkit and Astro for building editable, multi-editor sites on Cloudflare Workers.",
   "keywords": [
     "astro",
@@ -60,15 +60,15 @@
     "access": "public"
   },
   "dependencies": {
-    "louise-toolkit": "0.25.3"
+    "louise-toolkit": "0.27.0"
   },
   "devDependencies": {
     "@types/node": "^24.13.3",
     "@typescript/native-preview": "7.0.0-dev.20260707.2",
-    "astro": "^7.0.9",
-    "solid-js": "^1.9.14",
-    "typescript": "^5.8.0",
-    "vitest": "^4.1.10"
+    "astro": "^7.2.9",
+    "solid-js": "^1.9.15",
+    "typescript": "^5.9.3",
+    "vitest": "^4.1.11"
   },
   "peerDependencies": {
     "astro": "^7.0.9",