@ampless/runtime 0.2.0-alpha.1 → 0.2.0-alpha.3

package/dist/dispatchers/index.d.ts

@@ -1,3 +1,4 @@
+import { ReactNode } from 'react';
 import { Metadata } from 'next';
 import { Ampless } from '../index.js';
 import 'ampless';
@@ -7,16 +8,12 @@ interface Props$2 {
         siteId: string;
     }>;
 }
-type ThemeHomeDispatcher = (props: Props$2) => Promise<unknown>;
+type ThemeHomeDispatcher = (props: Props$2) => Promise<ReactNode>;
 type ThemeHomeMetadata = (props: Props$2) => Promise<Metadata>;
 /**
  * Home page dispatcher. Resolves the active theme for the request's
  * siteId and renders the theme's `components.Home` server component
  * with the same `params` Promise it was passed.
- *
- * The return type is `unknown` (cast at the route boundary) because
- * Next.js page-component prop types vary by route shape and the
- * underlying theme components are arbitrary server components.
  */
 declare function createThemeHomeDispatcher(ampless: Ampless): ThemeHomeDispatcher;
 /** generateMetadata factory for the home dispatcher. */
@@ -28,7 +25,7 @@ interface Props$1 {
         slug: string;
     }>;
 }
-type ThemePostDispatcher = (props: Props$1) => Promise<unknown>;
+type ThemePostDispatcher = (props: Props$1) => Promise<ReactNode>;
 type ThemePostMetadata = (props: Props$1) => Promise<Metadata>;
 /**
  * Post page dispatcher. Resolves the active theme and renders the
@@ -45,7 +42,7 @@ interface Props {
         tag: string;
     }>;
 }
-type ThemeTagDispatcher = (props: Props) => Promise<unknown>;
+type ThemeTagDispatcher = (props: Props) => Promise<ReactNode>;
 type ThemeTagMetadata = (props: Props) => Promise<Metadata>;
 /**
  * Tag page dispatcher. Resolves the active theme and renders the

package/dist/middleware.d.ts

@@ -21,14 +21,20 @@ type MiddlewareFn = (request: NextRequest) => NextResponse;
  */
 declare function createAmplessMiddleware({ cmsConfig }: CreateMiddlewareOpts): MiddlewareFn;
 /**
- * Default Next.js middleware matcher config. Exposed as a constant so
- * templates can re-export it directly:
+ * Reference matcher config — admin / api / login / static assets /
+ * amplify_outputs.json are excluded so middleware doesn't rewrite
+ * legitimate non-blog routes into the public site tree.
  *
- *     export const config = defaultMatcherConfig
+ * **You can't re-export this directly.** Next.js 16's Turbopack
+ * requires `export const config` in `proxy.ts` (or `middleware.ts`)
+ * to be a statically analysable object literal — referencing an
+ * imported variable fails the build with:
+ *   "Next.js can't recognize the exported `config` field in route.
+ *    It needs to be a static object."
  *
- * Excludes admin / api / login / static assets / amplify_outputs.json
- * — without these exclusions middleware would rewrite legitimate
- * non-blog routes into the public site tree.
+ * So the scaffold inlines the matcher into the user's `proxy.ts`.
+ * This export is kept as a reference for documentation and for
+ * non-Next.js callers that want to inspect the canonical matcher.
  */
 declare const defaultMatcherConfig: {
     matcher: string[];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ampless/runtime",
-  "version": "0.2.0-alpha.1",
+  "version": "0.2.0-alpha.3",
   "description": "Public-side runtime for ampless: post fetching, theme dispatch, middleware, public route handlers",
   "license": "MIT",
   "type": "module",