create-nextly-app 0.0.2-alpha.74 → 0.0.2-alpha.76

package/dist/index.cjs

@@ -1,3 +1,3 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-const require_create_nextly = require("./create-nextly-Decg8dye.cjs");
+const require_create_nextly = require("./create-nextly-CXsN4jfA.cjs");
 exports.createNextly = require_create_nextly.createNextly;

package/dist/index.mjs

@@ -1 +1 @@
-export { t as createNextly } from "./create-nextly-ChHdzG83.mjs";
+export { t as createNextly } from "./create-nextly-BmGN2BX8.mjs";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-nextly-app",
-  "version": "0.0.2-alpha.74",
+  "version": "0.0.2-alpha.76",
   "description": "CLI to scaffold Nextly in your Next.js project",
   "license": "MIT",
   "type": "module",
@@ -37,10 +37,10 @@
   },
   "devDependencies": {
     "@babel/types": "^7.29.7",
-    "@nextlyhq/eslint-plugin": "0.0.2-alpha.74",
-    "@nextlyhq/module-specifiers": "0.0.2-alpha.74",
-    "@nextlyhq/telemetry": "0.0.2-alpha.74",
-    "@nextlyhq/tsconfig": "0.0.2-alpha.74",
+    "@nextlyhq/eslint-plugin": "0.0.2-alpha.76",
+    "@nextlyhq/module-specifiers": "0.0.2-alpha.76",
+    "@nextlyhq/telemetry": "0.0.2-alpha.76",
+    "@nextlyhq/tsconfig": "0.0.2-alpha.76",
     "@testing-library/react": "^16.3.0",
     "@types/fs-extra": "^11.0.4",
     "@types/node": "^22.20.5",

package/skills/nextly-authentication/SKILL.md

@@ -7,7 +7,7 @@ description: >-
   code, and extra fields on users. Also use when asked to add login or
   sign-up to a Nextly site, so the answer matches what Nextly provides.
 metadata:
-  nextly-version: 0.0.2-alpha.74
+  nextly-version: 0.0.2-alpha.76
 ---
 
 # Authentication and access in Nextly

package/skills/nextly-collections/SKILL.md

@@ -9,7 +9,7 @@ description: >-
   not appear in the admin, a field change does not reach the database, or a
   page reading content fails to build.
 metadata:
-  nextly-version: 0.0.2-alpha.74
+  nextly-version: 0.0.2-alpha.76
 ---
 
 # Define a collection in Nextly

package/skills/nextly-deploy/SKILL.md

@@ -8,7 +8,7 @@ description: >-
   Also use when a deployed Nextly app has missing tables, refuses to start,
   or loses uploaded files.
 metadata:
-  nextly-version: 0.0.2-alpha.74
+  nextly-version: 0.0.2-alpha.76
 ---
 
 # Deploy a Nextly project

package/skills/nextly-install/SKILL.md

@@ -8,7 +8,7 @@ description: >-
   Nextly install shows no collections, fails to load nextly.config.ts, or its
   admin panel misbehaves after setup.
 metadata:
-  nextly-version: 0.0.2-alpha.74
+  nextly-version: 0.0.2-alpha.76
 ---
 
 # Install Nextly into an existing Next.js app

package/templates/base/src/app/admin/[[...params]]/layout.tsx

@@ -1,13 +1,48 @@
 import { connection } from "next/server";
 import { Suspense } from "react";
-import { getBrandingCss } from "nextly/config";
-import { checkAdminComponents } from "nextly/runtime";
+import {
+  ADMIN_BRANDING_ELEMENT_ID,
+  ADMIN_STARTUP_SCREENS_ELEMENT_ID,
+  adminBrandingJson,
+  adminMetadataFor,
+  adminStartupScreensJson,
+  getBrandingCss,
+} from "nextly/config";
 
 import config from "../../../../nextly.config";
 import { registeredComponentPaths } from "../../../types/generated/plugin-admin-components.generated";
 
 const brandingCss = getBrandingCss(config.admin?.branding);
+// The configured logo, name and favicon, read by the admin before any request
+// answers, so they are right from the first paint.
+const brandingJson = adminBrandingJson(config.admin?.branding);
+// What each plugin page reads as it opens, so the admin asks for it in its
+// first request when a tab opens on that page.
+const startupScreensJson = adminStartupScreensJson(config.plugins);
 
+/**
+ * The admin is never a page for search results: `noindex, nofollow` in the
+ * head of the first HTML the server sends, whatever plugins the site runs,
+ * and the configured favicon's link beside it.
+ */
+export const metadata = adminMetadataFor(config.admin?.branding);
+
+/**
+ * `/admin` itself is built ahead, so it is served from the build's files. The
+ * admin's other paths are drawn by the same page in the browser, and are
+ * served the same prebuilt shell.
+ */
+export function generateStaticParams(): { params: string[] }[] {
+  return [{ params: [] }];
+}
+
+/**
+ * Prebuilt in production: the same page for every visitor, built once, with
+ * no request-time work and nothing read from the database. Everything about
+ * the person comes from the admin's own requests once it loads, so a CDN or
+ * the browser may keep the page, and it is served while the server is still
+ * starting.
+ */
 export default function AdminLayout({
   children,
 }: {
@@ -18,25 +53,46 @@ export default function AdminLayout({
       {brandingCss && (
         <style dangerouslySetInnerHTML={{ __html: brandingCss }} />
       )}
-      <Suspense fallback={null}>
-        <ForThisRequest>{children}</ForThisRequest>
-      </Suspense>
+      {brandingJson && (
+        <script
+          type="application/json"
+          id={ADMIN_BRANDING_ELEMENT_ID}
+          dangerouslySetInnerHTML={{ __html: brandingJson }}
+        />
+      )}
+      {startupScreensJson && (
+        <script
+          type="application/json"
+          id={ADMIN_STARTUP_SCREENS_ELEMENT_ID}
+          dangerouslySetInnerHTML={{ __html: startupScreensJson }}
+        />
+      )}
+      {process.env.NODE_ENV === "development" ? (
+        <Suspense fallback={null}>
+          <ComponentMapKeptCurrent>{children}</ComponentMapKeptCurrent>
+        </Suspense>
+      ) : (
+        children
+      )}
     </>
   );
 }
 
 /**
- * The admin renders for each request, never from a cache another user's
- * request filled. Beneath the layout's Suspense boundary, so under Cache
- * Components the shell above it still prerenders: request work outside a
- * boundary fails the build, in development too, where `checkAdminComponents`
- * boots nextly.
+ * Development only: before any admin page, the generated component map is
+ * written again when it falls behind the config. A production build serves
+ * the map it was built with, so it drops this, and the page with it is
+ * prebuilt. Beneath a Suspense boundary, as request work outside one fails a
+ * Cache Components build, in development too. The check is loaded here, so a
+ * production page never loads the runtime it lives in.
  */
-async function ForThisRequest({ children }: { children: React.ReactNode }) {
+async function ComponentMapKeptCurrent({
+  children,
+}: {
+  children: React.ReactNode;
+}) {
   await connection();
-  // In development, the generated component map is written again when it
-  // falls behind the config, so a plugin added while `next dev` runs draws
-  // its components without a command. In production it does nothing.
+  const { checkAdminComponents } = await import("nextly/runtime");
   await checkAdminComponents({ config, registeredComponentPaths });
   return children;
 }

package/templates/base/src/types/generated/plugin-admin-imports.generated.ts

@@ -3,6 +3,7 @@
  * string (pages, settings, views, slots, field-type editors) so they load
  * without manual host imports. */
 
+import { registerComponentMap } from "@nextlyhq/admin";
 import { registeredComponentPaths as listed } from "./plugin-admin-components.generated";
 
 const registered = {};
@@ -29,4 +30,5 @@ if (
   );
 }
 
+registerComponentMap(registered);
 export const registeredComponentPaths = listed;

package/templates/blank/src/instrumentation.ts

@@ -26,8 +26,11 @@ export async function register(): Promise<void> {
   // Next.js writes its Cache Components setting into this file as it builds
   // it. Nextly, loaded from node_modules, cannot read that for itself. With
   // it off, Nextly warns at start; with it on, a cached read that finds no
-  // "use cache" read function says so.
+  // "use cache" read function says so. The same holds for the build's newest
+  // migration, which withNextly sets: a production start compares it with
+  // the database's schema version and warns when the database is behind.
   await createRegister(config, {
     cacheComponents: process.env.__NEXT_CACHE_COMPONENTS,
+    buildSchemaVersion: process.env.NEXTLY_BUILD_SCHEMA_VERSION,
   })();
 }

package/templates/plugin/AGENTS.md.template

@@ -41,8 +41,8 @@ working on an app.
 - **Plugin APIs come from `@nextlyhq/plugin-sdk`; schema APIs come from
   `nextly/config`.** The SDK is the stability boundary for everything a plugin
   does AS a plugin: `definePlugin`, field factories, `pluginField` and
-  `NextlyError` from `@nextlyhq/plugin-sdk`; `registerComponents` and
-  `registerKnownPlugin` from `@nextlyhq/plugin-sdk/admin`; `createTestNextly`
+  `NextlyError` from `@nextlyhq/plugin-sdk`; `registerComponents` from
+  `@nextlyhq/plugin-sdk/admin`; `createTestNextly`
   from `@nextlyhq/plugin-sdk/testing`. Collections and singles are defined the same way an app defines
   them, with `defineCollection` from `nextly/config` — which is what
   `src/collections/example.ts` does.

package/templates/plugin/dev/src/instrumentation.ts

@@ -10,9 +10,12 @@ export async function register(): Promise<void> {
   // Next.js writes its Cache Components setting into this file as it builds
   // it. Nextly, loaded from node_modules, cannot read that for itself. With
   // it off, Nextly warns at start; with it on, a cached read that finds no
-  // "use cache" read function says so.
+  // "use cache" read function says so. The same holds for the build's newest
+  // migration, which withNextly sets: a production start compares it with
+  // the database's schema version and warns when the database is behind.
   await createRegister(config, {
     cacheComponents: process.env.__NEXT_CACHE_COMPONENTS,
+    buildSchemaVersion: process.env.NEXTLY_BUILD_SCHEMA_VERSION,
   })();
 
   // Create the user admin.devAutoLogin signs in as (see seed-dev-user.ts).

package/templates/plugin/dev/src/types/generated/plugin-admin-imports.generated.ts

@@ -3,7 +3,7 @@
  * string (pages, settings, views, slots, field-type editors) so they load
  * without manual host imports. */
 
-import { registerComponents } from "@nextlyhq/admin";
+import { registerComponentMap } from "@nextlyhq/admin";
 import * as _p0 from "{{pluginName}}/admin";
 import { registeredComponentPaths as listed } from "./plugin-admin-components.generated";
 
@@ -33,5 +33,5 @@ if (
   );
 }
 
-registerComponents(registered);
+registerComponentMap(registered);
 export const registeredComponentPaths = listed;

package/templates/plugin/src/admin/index.ts

@@ -1,24 +1,14 @@
 /**
- * Admin component registration (D19/D60). Importing this module registers the
- * React components referenced by `contributes.admin` string paths so the host
- * admin can resolve them. The host's generated import map imports this for you;
- * the eager + lazy registration below is the fallback.
+ * Admin component registration. Importing this module registers the React
+ * components referenced by `contributes.admin` string paths so the host admin
+ * can resolve them. The host's generated component map imports it for you.
  */
-import {
-  registerComponents,
-  registerKnownPlugin,
-} from "@nextlyhq/plugin-sdk/admin";
+import { registerComponents } from "@nextlyhq/plugin-sdk/admin";
 
 import { SettingsPage } from "./SettingsPage";
 
 const SETTINGS_PATH = "{{pluginName}}/admin#SettingsPage";
 
-// Eager: register on module load.
 registerComponents({ [SETTINGS_PATH]: SettingsPage });
 
-// Lazy fallback: the host can trigger registration on demand by package prefix.
-registerKnownPlugin("{{pluginName}}", async () => {
-  registerComponents({ [SETTINGS_PATH]: SettingsPage });
-});
-
 export { SettingsPage };