@elytracms/cli 0.0.90 → 0.0.91

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@elytracms/cli",
   "author": "finaldream <hi@finaldream.de>",
-  "version": "0.0.90",
+  "version": "0.0.91",
   "description": "The Elytra CLI — run a consuming repo's studio, frontend, and Convex backend under one command.",
   "license": "MIT",
   "type": "module",
@@ -17,7 +17,7 @@
     "node": ">=22.18.0"
   },
   "dependencies": {
-    "@elytracms/core": "^0.0.90"
+    "@elytracms/core": "^0.0.91"
   },
   "devDependencies": {
     "vitest": "^4.1.10"

package/src/doctor.js

@@ -497,6 +497,73 @@ export async function routeFactsFor({ outcome, configFacts = {}, routeFacts, roo
   return { ...enriched, source: 'native' }
 }
 
+// --- Frontend: `cacheComponents` (EC-515) --------------------------------------
+
+/** The `next.config` file names Next itself resolves, in its order. */
+export const NEXT_CONFIG_FILES = ['next.config.js', 'next.config.mjs', 'next.config.ts', 'next.config.mts', 'next.config.cjs']
+
+/**
+ * Read the frontend's `next.config` for the `cacheComponents` check — the file name and
+ * its text, or `{ configFile: null }` when the app has none. `undefined` when there is no
+ * frontend app to read (a studio-only repo: no row at all). Text only: the CLI runs
+ * without the consumer's `node_modules`, and a `next.config` imports Next-side modules.
+ * `readFile` is injectable for tests.
+ */
+export function gatherFrontendCacheComponents(frontendDir, readFile = (p) => readFileSync(p, 'utf8')) {
+  if (!frontendDir) return undefined
+  for (const name of NEXT_CONFIG_FILES) {
+    try {
+      return { configFile: name, text: readFile(join(frontendDir, name)) }
+    } catch {
+      // not this name — try the next
+    }
+  }
+  return { configFile: null, text: '' }
+}
+
+/**
+ * The `frontend-cache-components` row (`app` bucket). Since EC-515 the delivery kit's
+ * cache is a `'use cache'` entry, which Next compiles only with `cacheComponents: true`
+ * — without it `next build` fails under both bundlers (measured: "To use "use cache",
+ * please enable the feature flag `cacheComponents`"). So a missing flag is a `fail`:
+ * deterministic in the repo, and the build would fail anyway — so is a literal `false`. A
+ * `cacheComponents` key that is neither literal (computed from env, say) is a `warn` —
+ * the doctor reads text and cannot evaluate it. No frontend → no row. Pure.
+ */
+export function cacheComponentsDoctorChecks(facts, { frontendLabel = 'frontend' } = {}) {
+  if (!facts) return []
+  const base = { id: 'frontend-cache-components', bucket: 'app' }
+  const fix = `Set \`cacheComponents: true\` in ${frontendLabel}/next.config.mjs, and export \`generateStaticParams = route.generateStaticParams\` from the canvas catch-all page (see the upgrading notes for EC-515).`
+  if (facts.configFile === null) {
+    return [{ ...base, status: 'fail', detail: `${frontendLabel} has no next.config — the delivery kit needs \`cacheComponents: true\`.`, fix }]
+  }
+  const where = `${frontendLabel}/${facts.configFile}`
+  if (/\bcacheComponents\s*:\s*true\b/.test(facts.text)) {
+    return [{ ...base, status: 'ok', detail: `${where} enables \`cacheComponents\` (the kit's 'use cache' delivery cache).` }]
+  }
+  if (/\bcacheComponents\s*:\s*false\b/.test(facts.text)) {
+    return [{ ...base, status: 'fail', detail: `${where} sets \`cacheComponents: false\` — \`next build\` fails on the delivery kit's 'use cache' cache.`, fix }]
+  }
+  if (/\bcacheComponents\b/.test(facts.text)) {
+    return [
+      {
+        ...base,
+        status: 'warn',
+        detail: `${where} sets \`cacheComponents\` to something other than the literal \`true\` — the doctor cannot evaluate it. \`next build\` fails if it is not true.`,
+        fix,
+      },
+    ]
+  }
+  return [
+    {
+      ...base,
+      status: 'fail',
+      detail: `${where} does not enable \`cacheComponents\` — \`next build\` fails on the delivery kit's 'use cache' cache.`,
+      fix,
+    },
+  ]
+}
+
 // --- Command -----------------------------------------------------------------
 
 /**
@@ -553,6 +620,12 @@ export async function routeFactsFor({ outcome, configFacts = {}, routeFacts, roo
  *  - the route checks run over the RESOLVED config's routes whenever the harness
  *    resolved it (the routes the studio and delivery actually serve); the native
  *    `cms/index.ts` read is the fallback only when it could not, and the row says which.
+ *
+ * EC-515: when the layout resolved a frontend app, the `app` bucket reports
+ * `frontend-cache-components` — whether its `next.config` enables `cacheComponents`,
+ * which the delivery kit's `'use cache'` cache requires ({@link
+ * cacheComponentsDoctorChecks}). `frontendCacheComponents` (the gathered facts) is the
+ * test seam.
  */
 export async function runDoctor({
   env = {},
@@ -569,6 +642,7 @@ export async function runDoctor({
   routeFacts,
   configOutcome,
   installedEngineVersion,
+  frontendCacheComponents,
 } = {}) {
   const studioLabel = appDisplay(layout, 'studio')
   const target = resolveDoctorTarget(env, { url, envSource: `${studioLabel}/.env` })
@@ -638,9 +712,15 @@ export async function runDoctor({
   let checks = artifacts ? [...report.checks, ...previewsDoctorChecks(artifacts)] : [...report.checks]
 
   // EC-603: the layout and AI-route rows, in the `app` bucket (both repo facts).
+  // EC-515: the frontend's `cacheComponents` flag — a repo fact, any backend mode.
+  const frontend = layout?.entries?.frontend
   checks = spliceBucketChecks(checks, 'app', [
     ...layoutDoctorChecks(layout),
     ...aiRouteDoctorChecks(aiRoute, { studioLabel }),
+    ...cacheComponentsDoctorChecks(
+      frontendCacheComponents ?? gatherFrontendCacheComponents(frontend?.found ? frontend.path : undefined),
+      { frontendLabel: appDisplay(layout, 'frontend') },
+    ),
   ])
 
   // EC-469: the route-conflict check, spliced into the `app` bucket it belongs to.