@ampless/backend 0.2.0-alpha.1 → 0.2.0-alpha.2

package/dist/events/processor-trusted.d.ts

@@ -1,5 +1,5 @@
 import { SQSHandler } from 'aws-lambda';
-import { AmplessPlugin, Config } from 'ampless';
+import { Config } from 'ampless';
 
 interface CreateProcessorTrustedHandlerOpts {
     /**
@@ -7,8 +7,12 @@ interface CreateProcessorTrustedHandlerOpts {
      * trusted plugins itself so callers don't need to remember the
      * filter, and so adding `privileged` later only touches the handler
      * code in this package.
+     *
+     * Accepts the raw `Config['plugins']` shape (which permits string
+     * entries for future dynamic loading) — the runtime filter discards
+     * anything that isn't a plugin object.
      */
-    plugins?: AmplessPlugin[];
+    plugins?: Config['plugins'];
     /**
      * The `cms.config.site` block, surfaced to plugin hooks via
      * `ctx.site`. Pass through from the thin shell — handlers must

package/dist/events/processor-untrusted.d.ts

@@ -1,12 +1,16 @@
 import { SQSHandler } from 'aws-lambda';
-import { AmplessPlugin, Config } from 'ampless';
+import { Config } from 'ampless';
 
 interface CreateProcessorUntrustedHandlerOpts {
     /**
      * The full `cms.config.plugins` array. The handler filters down to
      * untrusted plugins itself.
+     *
+     * Accepts the raw `Config['plugins']` shape (which permits string
+     * entries for future dynamic loading) — the runtime filter discards
+     * anything that isn't a plugin object.
      */
-    plugins?: AmplessPlugin[];
+    plugins?: Config['plugins'];
     /**
      * The `cms.config.site` block, surfaced to plugin hooks via
      * `ctx.site` (read-only — untrusted plugins have no AWS-touching

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ampless/backend",
-  "version": "0.2.0-alpha.1",
+  "version": "0.2.0-alpha.2",
   "description": "Amplify Gen 2 backend factories for ampless: auth, data, storage, event processors, API key renewer",
   "license": "MIT",
   "type": "module",