create-ampless 0.2.0-alpha.0 → 0.2.0-alpha.10

package/dist/templates/_shared/amplify/auth/resource.ts

@@ -1,8 +1,13 @@
-import { defineAmplessAuth } from '@ampless/backend'
+import { defineAuth } from '@aws-amplify/backend'
+import { amplessAuthConfig } from '@ampless/backend'
 import { postConfirmation } from './post-confirmation/resource.js'
 
 // Provisions a Cognito User Pool + Identity Pool with the three role
 // groups (ampless-admin, ampless-editor, ampless-reader) and wires in
 // the post-confirmation Lambda that promotes the first confirmed user
 // to ampless-admin.
-export const auth = defineAmplessAuth({ postConfirmation })
+//
+// `defineAuth` must be called from this file directly — Amplify Gen 2's
+// import-path verifier requires it to live at amplify/auth/resource.ts.
+// `amplessAuthConfig` just returns the props object.
+export const auth = defineAuth(amplessAuthConfig({ postConfirmation }))

package/dist/templates/_shared/amplify/backend.custom.ts

@@ -0,0 +1,41 @@
+import type { AmplessBackend } from '@ampless/backend'
+
+// Custom backend extensions for this project.
+//
+// `amplify/backend.ts` calls `customizeBackend(backend)` right after
+// ampless's baseline wiring. Mutate the passed `backend` instance to
+// add Lambda permissions, attach event sources, register custom CDK
+// constructs, etc.
+//
+// This file is NEVER overwritten by `create-ampless upgrade` —
+// `amplify/backend.ts` is, so keep your customizations here.
+//
+// (Function-export rather than side-effect import on purpose: a
+// top-level `import { backend } from './backend.js'` would create an
+// ESM circular dependency, leaving `backend` in its TDZ at evaluation
+// time. The factory pattern sidesteps that.)
+//
+// Example: granting an existing ampless Lambda extra IAM permissions:
+//
+//   import { Effect, PolicyStatement } from 'aws-cdk-lib/aws-iam'
+//
+//   export function customizeBackend(backend: AmplessBackend): void {
+//     backend.processorTrusted.resources.lambda.addToRolePolicy(
+//       new PolicyStatement({
+//         effect: Effect.ALLOW,
+//         actions: ['ses:SendEmail'],
+//         resources: ['*'],
+//       })
+//     )
+//   }
+//
+// Example: adding your own Lambda function — define it in
+// `amplify/functions/<name>/resource.ts`, import it here, and attach
+// it inside `customizeBackend` via `backend.createStack(...)` or by
+// granting it permissions on existing resources.
+//
+// If you don't need any extensions, leave the body empty.
+
+export function customizeBackend(_backend: AmplessBackend): void {
+  // No-op by default.
+}

package/dist/templates/_shared/amplify/backend.ts

@@ -8,13 +8,16 @@ import { eventDispatcher } from './events/dispatcher/resource.js'
 import { processorTrusted } from './events/processor-trusted/resource.js'
 import { processorUntrusted } from './events/processor-untrusted/resource.js'
 import { apiKeyRenewer } from './functions/api-key-renewer/resource.js'
+import { userAdmin } from './functions/user-admin/resource.js'
+import { customizeBackend } from './backend.custom.js'
 
 // `defineAmplessBackend` provisions auth, data, storage, the event
 // system (DynamoDB Streams → SQS-trusted / SQS-untrusted → trust_level
 // Lambdas), the AppSync API key renewer, and every IAM / CORS /
 // password policy override. Add custom CDK constructs / IAM policies
-// below by mutating the returned `backend` — `defineAmplessBackend`
-// returns the same object Amplify Gen 2's `defineBackend` does.
+// in `amplify/backend.custom.ts` by mutating the `backend` instance —
+// `defineAmplessBackend` returns the same object Amplify Gen 2's
+// `defineBackend` does.
 const backend = defineAmplessBackend({
   auth,
   data,
@@ -24,6 +27,11 @@ const backend = defineAmplessBackend({
   processorTrusted,
   processorUntrusted,
   apiKeyRenewer,
+  userAdmin,
 })
 
+// Run user-defined customizations after baseline wiring. `backend.custom.ts`
+// is never overwritten by `create-ampless upgrade`.
+customizeBackend(backend)
+
 export default backend

package/dist/templates/_shared/amplify/data/resource.custom.ts

@@ -0,0 +1,33 @@
+// Custom data schema models for this project.
+//
+// `amplify/data/resource.ts` calls `customSchemaModels(a)` and spreads
+// the result alongside ampless's built-in models in the same
+// `a.schema({...})` call, which is the only way Amplify Gen 2's
+// `ClientSchema<typeof schema>` inference picks up extra models.
+//
+// This file is NEVER overwritten by `create-ampless upgrade` —
+// `amplify/data/resource.ts` is, so keep your custom models here.
+//
+// Example:
+//
+//   export function customSchemaModels(a: any) {
+//     return {
+//       Bookmark: a
+//         .model({
+//           siteId: a.string().required(),
+//           bookmarkId: a.id().required(),
+//           url: a.string().required(),
+//           title: a.string(),
+//         })
+//         .identifier(['siteId', 'bookmarkId'])
+//         .authorization((allow: any) => [allow.groups(['ampless-admin', 'ampless-editor'])]),
+//     }
+//   }
+//
+// `a` is the Amplify Gen 2 schema builder; see Amplify Data docs for
+// the full DSL. Return an empty object if no customizations are needed.
+
+// eslint-disable-next-line @typescript-eslint/no-explicit-any
+export function customSchemaModels(_a: any): Record<string, unknown> {
+  return {}
+}

package/dist/templates/_shared/amplify/data/resource.ts

@@ -1,26 +1,34 @@
+import { fileURLToPath } from 'node:url'
+import { dirname, resolve } from 'node:path'
 import { a, defineData, type ClientSchema } from '@aws-amplify/backend'
 import { amplessSchemaModels, defaultAuthorizationModes } from '@ampless/backend'
+import { userAdmin } from '../functions/user-admin/resource.js'
+import { customSchemaModels } from './resource.custom.js'
+
+// AppSync's `a.handler.custom({ entry })` paths are resolved by CDK
+// relative to the file that called `a.handler.custom`. When the call
+// originates inside `@ampless/backend` (via amplessSchemaModels), the
+// CDK synth tries to resolve `./list-published-posts.js` relative to
+// `node_modules/@ampless/backend/dist/index.js` and fails with
+// `UnresolvedEntryPathError`. Anchor the resolver paths at THIS file's
+// directory so the result is unambiguous.
+const __dirname = dirname(fileURLToPath(import.meta.url))
 
 // Ampless's built-in models (Post / Page / Media / Taxonomy / PostTag /
 // KvStore) plus the three public-read custom queries
 // (listPublishedPosts / getPublishedPost / listPostsByTag).
 //
-// Add project-specific models alongside the spread:
-//
-//   const schema = a.schema({
-//     ...amplessSchemaModels(a),
-//     MyCustomModel: a
-//       .model({ siteId: a.string().required(), foo: a.string() })
-//       .identifier(['siteId', 'foo'])
-//       .authorization((allow) => [allow.groups(['ampless-admin'])]),
-//   })
-//
-// The three AppSync JS resolvers (`*.js` in this directory) stay
-// user-owned — AppSync resolves `entry: './...'` paths at synth time
-// relative to this file. If you relocate them, pass new paths via
-// `amplessSchemaModels(a, { resolverPaths: { ... } })`.
+// Add project-specific models in `amplify/data/resource.custom.ts` —
+// that file is never overwritten by `create-ampless upgrade`.
+const resolverPaths = {
+  listPublishedPosts: resolve(__dirname, 'list-published-posts.js'),
+  getPublishedPost: resolve(__dirname, 'get-published-post.js'),
+  listPostsByTag: resolve(__dirname, 'list-posts-by-tag.js'),
+}
+
 const schema = a.schema({
-  ...amplessSchemaModels(a),
+  ...amplessSchemaModels(a, { resolverPaths, userAdminFunction: userAdmin }),
+  ...customSchemaModels(a),
 })
 
 export type Schema = ClientSchema<typeof schema>

package/dist/templates/_shared/amplify/functions/user-admin/handler.ts

@@ -0,0 +1,4 @@
+// Re-exported from @ampless/backend so the package can ship Lambda
+// handler updates via `npm update`. Amplify's esbuild follows this
+// import and bundles the real handler into the Lambda artifact.
+export { handler } from '@ampless/backend/auth/user-admin'

package/dist/templates/_shared/amplify/functions/user-admin/resource.ts

@@ -0,0 +1,6 @@
+import { defineFunction } from '@aws-amplify/backend'
+
+export const userAdmin = defineFunction({
+  name: 'user-admin',
+  entry: './handler.ts',
+})

package/dist/templates/_shared/amplify/storage/resource.ts

@@ -1,7 +1,12 @@
-import { defineAmplessStorage } from '@ampless/backend'
+import { defineStorage } from '@aws-amplify/backend'
+import { amplessStorageConfig } from '@ampless/backend'
 
 // Provisions the ampless media + plugins bucket with guest read on
 // `public/*` and admin/editor write on the matched prefixes. CORS and
 // the bucket-level public-access policy are applied by
 // defineAmplessBackend.
-export const storage = defineAmplessStorage()
+//
+// `defineStorage` must be called from this file directly — Amplify Gen 2's
+// import-path verifier requires it to live at amplify/storage/resource.ts.
+// `amplessStorageConfig` just returns the props object.
+export const storage = defineStorage(amplessStorageConfig())

package/dist/templates/_shared/amplify.yml

@@ -0,0 +1,18 @@
+version: 1
+frontend:
+  phases:
+    preBuild:
+      commands:
+        - npm install
+    build:
+      commands:
+        - npx ampx pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID
+        - npm run build
+  artifacts:
+    baseDirectory: .next
+    files:
+      - '**/*'
+  cache:
+    paths:
+      - node_modules/**/*
+      - .next/cache/**/*

package/dist/templates/_shared/app/(admin)/admin/users/page.tsx

@@ -0,0 +1,5 @@
+import { admin } from '@/lib/admin'
+import { createUsersListPage } from '@ampless/admin/pages'
+
+export const dynamic = 'force-dynamic'
+export default createUsersListPage(admin)

package/dist/templates/_shared/app/site/[siteId]/[...path]/route.ts

@@ -0,0 +1,17 @@
+import { ampless } from '@/lib/ampless'
+import { createStaticRouteHandler } from '@ampless/runtime/routes'
+
+// Catch-all handler for `format: 'static'` post bundles. Lives here
+// instead of under a dedicated `/static/` prefix so the published URL
+// stays a clean `/<slug>/…`, matching how a developer would host a
+// hand-written landing page locally. The runtime handler enforces
+// `format === 'static'` and 404s for any other post format reaching
+// this route.
+//
+// Routing precedence: Next.js prefers the more specific
+// `[siteId]/[slug]/page.tsx` for single-segment URLs, so the regular
+// theme post dispatcher keeps handling normal posts. This catch-all
+// only fires for multi-segment requests (e.g. `/promo/index.html`,
+// `/promo/assets/style.css`).
+export const dynamic = 'force-dynamic'
+export const GET = createStaticRouteHandler(ampless)

package/dist/templates/_shared/components/i18n-provider.tsx

@@ -1,7 +1,15 @@
+'use client'
+
 // Back-compat shim. I18n provider + hooks moved to `@ampless/admin`
 // (L2 extraction). The component tree mounts the provider inside the
 // admin layout factory; the root layout in `app/layout.tsx` still
 // wraps the public site in this same provider to keep client-side
 // `useT()` calls working from theme-side components too.
+//
+// The `'use client'` directive is needed because the bundled
+// @ampless/admin/components ESM strips per-file 'use client' (tsup
+// default behaviour). This shim re-establishes a client boundary so
+// Next.js doesn't try to evaluate the React hooks inside an RSC
+// server context.
 
 export { I18nProvider, useT, useLocale } from '@ampless/admin/components'

package/dist/templates/_shared/lib/admin-site.ts

@@ -4,5 +4,9 @@
 
 import { admin } from './admin'
 
-export const currentAdminSiteId = admin.currentAdminSiteId.bind(admin)
-export const adminSiteOptions = admin.adminSiteOptions.bind(admin)
+// Arrow wrappers: defer `admin` resolution to call time (avoid TDZ in
+// case of circular import chains touching admin shims).
+export const currentAdminSiteId: typeof admin.currentAdminSiteId =
+  (...args) => admin.currentAdminSiteId(...args)
+export const adminSiteOptions: typeof admin.adminSiteOptions =
+  (...args) => admin.adminSiteOptions(...args)

package/dist/templates/_shared/lib/admin.ts

@@ -4,18 +4,24 @@
 //
 // L2 architectural change (admin extraction): admin UI now lives in
 // `@ampless/admin`. This module wires the project's
-// `amplify_outputs.json`, `cms.config`, and `ampless` runtime into a
-// single `Admin` instance.
+// `amplify_outputs.json` and `cms.config` into a single `Admin`
+// instance.
+//
+// NOTE: We intentionally do NOT pass an `ampless` instance to
+// createAdmin. That would import `lib/ampless.ts`, which imports
+// `themes-registry`, which (via theme pages → `lib/i18n.ts`) imports
+// back to this file — a circular chain that crashes with a TDZ
+// ReferenceError on `ampless` at module init. `createAdmin` builds
+// its own internal Ampless when omitted, which is functionally
+// equivalent for admin's needs.
 
 import outputs from '../amplify_outputs.json'
 import cmsConfig from '@/cms.config'
 import { createAdmin } from '@ampless/admin'
-import { ampless } from './ampless'
 
 export const admin = createAdmin({
   outputs,
   cmsConfig,
-  ampless,
   locale: (cmsConfig as { locale?: string }).locale ?? 'en',
 })
 

package/dist/templates/_shared/lib/amplify.ts

@@ -1,9 +1,20 @@
-// Back-compat shim. The Amplify SDK is now configured by the admin's
-// `<AdminProviders>` bootstrap (mounted by the layout factory in
-// `@ampless/admin/pages`), so most call sites no longer need to call
-// `configureAmplify()` themselves. Kept as a no-op so any lingering
-// `import '@/lib/amplify'` side-effect imports stay safe.
+// Client-side Amplify SDK setup. Imported as a side-effect from
+// `app/providers.tsx` so it runs on every page load (public + admin +
+// login). `<AdminProviders>` (mounted by the admin layout factory)
+// also performs this configuration, but it only runs for routes under
+// the (admin) group; `/login` is a top-level route outside that group
+// and would otherwise hit "Auth UserPool not configured" because no
+// AdminProviders has bootstrapped the SDK yet.
+//
+// `Amplify.configure` is idempotent — calling it once at the root and
+// again inside AdminProviders is harmless.
+
+import { Amplify } from 'aws-amplify'
+import outputs from '../amplify_outputs.json'
+
+Amplify.configure(outputs, { ssr: true })
 
 export function configureAmplify() {
-  // intentionally empty — admin bootstrap handles this
+  // module-level side effect above already ran; keep this as a no-op
+  // for callers that still import it as a function for back-compat.
 }

package/dist/templates/_shared/lib/auth-server.ts

@@ -6,6 +6,10 @@ import { admin } from './admin'
 
 export type { ServerSession } from '@ampless/admin'
 
-export const getServerSession = admin.getServerSession.bind(admin)
-export const isAdmin = admin.isAdmin.bind(admin)
-export const isEditor = admin.isEditor.bind(admin)
+// Arrow wrappers: defer `admin` resolution to call time (avoid TDZ).
+export const getServerSession: typeof admin.getServerSession =
+  (...args) => admin.getServerSession(...args)
+export const isAdmin: typeof admin.isAdmin =
+  (...args) => admin.isAdmin(...args)
+export const isEditor: typeof admin.isEditor =
+  (...args) => admin.isEditor(...args)

package/dist/templates/_shared/lib/i18n.ts

@@ -20,7 +20,11 @@ export function getDictionary(locale: Locale = admin.locale): Dictionary {
   return adminGetDictionary(locale)
 }
 
-export const t = admin.t
+// Arrow wrapper: defer `admin` resolution to call time. If a future
+// circular import chain triggers i18n.ts before admin.ts has finished
+// initialising, eager `admin.t` would TDZ; calling the method through
+// a wrapper avoids that.
+export const t: typeof admin.t = (key, vars) => admin.t(key, vars)
 
 export function translate(
   _dict: Dictionary,

package/dist/templates/_shared/lib/posts-public.ts

@@ -8,9 +8,17 @@
 
 import { ampless } from './ampless'
 
-export const listPublishedPosts = ampless.listPublishedPosts.bind(ampless)
-export const getPublishedPost = ampless.getPublishedPost.bind(ampless)
-export const listPostsByTag = ampless.listPostsByTag.bind(ampless)
+// Arrow function wrappers (not `.bind(ampless)`) so the `ampless`
+// binding is read at call time, not at module evaluation. Module
+// evaluation can run while `lib/ampless.ts` is still in its TDZ
+// because the themes-registry → theme → shim → ampless dependency
+// chain is circular by construction.
+export const listPublishedPosts: typeof ampless.listPublishedPosts =
+  (...args) => ampless.listPublishedPosts(...args)
+export const getPublishedPost: typeof ampless.getPublishedPost =
+  (...args) => ampless.getPublishedPost(...args)
+export const listPostsByTag: typeof ampless.listPostsByTag =
+  (...args) => ampless.listPostsByTag(...args)
 
 export type {
   ListPostsOptions,

package/dist/templates/_shared/lib/seo.ts

@@ -4,5 +4,8 @@
 
 import { ampless } from './ampless'
 
-export const postMetadata = ampless.postMetadata.bind(ampless)
-export const siteMetadata = ampless.siteMetadata.bind(ampless)
+// Arrow wrappers: defer `ampless` resolution to call time (avoid TDZ).
+export const postMetadata: typeof ampless.postMetadata =
+  (...args) => ampless.postMetadata(...args)
+export const siteMetadata: typeof ampless.siteMetadata =
+  (...args) => ampless.siteMetadata(...args)

package/dist/templates/_shared/lib/site-settings.ts

@@ -3,6 +3,9 @@
 
 import { ampless } from './ampless'
 
-export const loadSiteSettings = ampless.loadSiteSettings.bind(ampless)
+// Arrow wrapper: defer `ampless` resolution to call time (avoid TDZ in
+// the themes-registry → theme → shim → ampless circular import chain).
+export const loadSiteSettings: typeof ampless.loadSiteSettings =
+  (...args) => ampless.loadSiteSettings(...args)
 
 export type { EffectiveSiteSettings } from '@ampless/runtime'

package/dist/templates/_shared/lib/storage.ts

@@ -3,5 +3,8 @@
 
 import { ampless } from './ampless'
 
-export const publicAssetUrl = ampless.publicAssetUrl.bind(ampless)
-export const isStorageConfigured = ampless.isStorageConfigured.bind(ampless)
+// Arrow wrappers: defer `ampless` resolution to call time (avoid TDZ).
+export const publicAssetUrl: typeof ampless.publicAssetUrl =
+  (...args) => ampless.publicAssetUrl(...args)
+export const isStorageConfigured: typeof ampless.isStorageConfigured =
+  (...args) => ampless.isStorageConfigured(...args)

package/dist/templates/_shared/lib/theme-active.ts

@@ -3,6 +3,8 @@
 
 import { ampless } from './ampless'
 
-export const resolveActiveTheme = ampless.resolveActiveTheme.bind(ampless)
+// Arrow wrapper: defer `ampless` resolution to call time (avoid TDZ).
+export const resolveActiveTheme: typeof ampless.resolveActiveTheme =
+  (...args) => ampless.resolveActiveTheme(...args)
 
 export type { ResolvedTheme } from '@ampless/runtime'

package/dist/templates/_shared/lib/theme-config.ts

@@ -3,7 +3,9 @@
 
 import { ampless } from './ampless'
 
-export const loadThemeConfig = ampless.loadThemeConfig.bind(ampless)
+// Arrow wrapper: defer `ampless` resolution to call time (avoid TDZ).
+export const loadThemeConfig: typeof ampless.loadThemeConfig =
+  (...args) => ampless.loadThemeConfig(...args)
 
 export { renderThemeCss } from '@ampless/runtime'
 

package/dist/templates/_shared/package.json

@@ -8,36 +8,39 @@
     "build": "next build",
     "start": "next start",
     "lint": "next lint",
-    "sandbox": "ampx sandbox"
+    "sandbox": "ampx sandbox",
+    "sandbox:dev": "ampx sandbox --once && next dev",
+    "update-ampless": "npx create-ampless@latest upgrade",
+    "copy-theme": "npx create-ampless@latest copy-theme"
   },
   "dependencies": {
     "@aws-amplify/adapter-nextjs": "^1.6.0",
     "@radix-ui/react-dialog": "^1.1.4",
     "@radix-ui/react-label": "^2.1.1",
     "@radix-ui/react-slot": "^1.1.1",
-    "@tiptap/extension-image": "^2.10.4",
-    "@tiptap/extension-link": "^2.10.4",
-    "@tiptap/pm": "^2.10.4",
-    "@tiptap/react": "^2.10.4",
-    "@tiptap/starter-kit": "^2.10.4",
-    "@ampless/plugin-og-image": "^0.2.0-alpha.0",
-    "@ampless/plugin-rss": "^0.2.0-alpha.0",
-    "@ampless/plugin-seo": "^0.2.0-alpha.0",
-    "@ampless/plugin-webhook": "^0.2.0-alpha.0",
-    "@ampless/admin": "^0.2.0-alpha.0",
-    "@ampless/backend": "^0.2.0-alpha.0",
-    "@ampless/runtime": "^0.2.0-alpha.0",
+    "@tiptap/extension-image": "^3.23.4",
+    "@tiptap/extension-link": "^3.23.4",
+    "@tiptap/pm": "^3.23.4",
+    "@tiptap/react": "^3.23.4",
+    "@tiptap/starter-kit": "^3.23.4",
+    "@ampless/plugin-og-image": "^0.2.0-alpha.3",
+    "@ampless/plugin-rss": "^0.2.0-alpha.3",
+    "@ampless/plugin-seo": "^0.2.0-alpha.3",
+    "@ampless/plugin-webhook": "^0.2.0-alpha.3",
+    "@ampless/admin": "^0.2.0-alpha.10",
+    "@ampless/backend": "^0.2.0-alpha.4",
+    "@ampless/runtime": "^0.2.0-alpha.5",
     "@digital-go-jp/tailwind-theme-plugin": "^0.3.4",
-    "ampless": "^0.2.0-alpha.0",
+    "ampless": "^0.2.0-alpha.3",
     "aws-amplify": "^6.10.0",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
-    "lucide-react": "^0.469.0",
-    "next": "^15.1.0",
+    "lucide-react": "^1.16.0",
+    "next": "^16.2.6",
     "react": "^19.0.0",
     "react-dom": "^19.0.0",
     "react-image-crop": "^11.0.7",
-    "tailwind-merge": "^2.6.0"
+    "tailwind-merge": "^3.6.0"
   },
   "devDependencies": {
     "@aws-amplify/backend": "^1.13.0",
@@ -45,7 +48,7 @@
     "@aws-sdk/client-appsync": "^3.717.0",
     "@aws-sdk/client-cognito-identity-provider": "^3.717.0",
     "@aws-sdk/client-dynamodb": "^3.717.0",
-    "@aws-sdk/client-s3": "^3.717.0",
+    "@aws-sdk/client-s3": "^3.1048.0",
     "@aws-sdk/client-sqs": "^3.717.0",
     "@aws-sdk/lib-dynamodb": "^3.717.0",
     "@aws-sdk/util-dynamodb": "^3.717.0",
@@ -58,6 +61,6 @@
     "aws-cdk-lib": "^2.174.0",
     "postcss": "^8.4.0",
     "tailwindcss": "^4.0.0",
-    "typescript": "^5.7.0"
+    "typescript": "^6.0.3"
   }
 }

package/dist/templates/_shared/proxy.ts

@@ -0,0 +1,33 @@
+// Public-site proxy (Next.js 16 rename of "middleware"). Implementation
+// moved to `@ampless/runtime` (L1 extraction); this file wires the
+// project's `cms.config` into the factory and re-exports the default
+// matcher. The runtime export name is still `createAmplessMiddleware`
+// for API stability; only the user-side file convention (proxy.ts +
+// `export const proxy`) follows Next 16's rename.
+//
+// See `@ampless/runtime/middleware` for behaviour details: multi-site
+// host rewrite, `<slug>.html` → raw route, `?previewTheme=` header
+// forwarding, multi-site Cache-Control override.
+
+import cmsConfig from './cms.config'
+import { createAmplessMiddleware } from '@ampless/runtime/middleware'
+
+export const proxy = createAmplessMiddleware({ cmsConfig })
+
+// Next.js 16's Turbopack requires `config` to be a statically
+// analysable object literal — referencing an imported variable
+// (e.g. `defaultMatcherConfig` from @ampless/runtime/middleware)
+// causes a build error:
+//   "Next.js can't recognize the exported `config` field in route.
+//    It needs to be a static object."
+//
+// So we inline the matcher here. If you change it, keep it in sync
+// with `defaultMatcherConfig` documented in @ampless/runtime/middleware.
+// The matcher excludes admin / api / login / static assets /
+// amplify_outputs.json so the public-site proxy doesn't rewrite
+// legitimate non-blog routes.
+export const config = {
+  matcher: [
+    '/((?!admin|api|login|_next/static|_next/image|favicon\\.ico|amplify_outputs\\.json).*)',
+  ],
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-ampless",
-  "version": "0.2.0-alpha.0",
+  "version": "0.2.0-alpha.10",
   "description": "Create a new ampless project",
   "license": "MIT",
   "type": "module",
@@ -22,7 +22,8 @@
   "homepage": "https://github.com/heavymoons/ampless#readme",
   "bugs": "https://github.com/heavymoons/ampless/issues",
   "dependencies": {
-    "@clack/prompts": "^0.9.1",
+    "@clack/prompts": "^1.4.0",
+    "execa": "^9.6.1",
     "picocolors": "^1.1.1"
   },
   "keywords": [

package/dist/templates/_shared/middleware.ts

@@ -1,13 +0,0 @@
-// Public-site middleware. Implementation moved to `@ampless/runtime`
-// (L1 extraction); this file wires the project's `cms.config` into
-// the factory and re-exports the default matcher.
-//
-// See `@ampless/runtime/middleware` for behaviour details: multi-site
-// host rewrite, `<slug>.html` → raw route, `?previewTheme=` header
-// forwarding, multi-site Cache-Control override.
-
-import cmsConfig from './cms.config'
-import { createAmplessMiddleware, defaultMatcherConfig } from '@ampless/runtime/middleware'
-
-export const middleware = createAmplessMiddleware({ cmsConfig })
-export const config = defaultMatcherConfig