create-nextly-app 0.0.2-alpha.62 → 0.0.2-alpha.64

package/dist/index.mjs

@@ -1,5 +1,5 @@
 import { createRequire } from 'module';
-export { createNextly } from './chunk-CTBK76CF.mjs';
+export { createNextly } from './chunk-I2U7KBH6.mjs';
 
 createRequire(import.meta.url);
 //# sourceMappingURL=index.mjs.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-nextly-app",
-  "version": "0.0.2-alpha.62",
+  "version": "0.0.2-alpha.64",
   "description": "CLI to scaffold Nextly in your Next.js project",
   "license": "MIT",
   "type": "module",
@@ -42,10 +42,10 @@
     "typescript": "^5.9.3",
     "vite-tsconfig-paths": "^5.1.4",
     "vitest": "^4.1.0",
-    "@nextlyhq/eslint-config": "0.0.2-alpha.62",
-    "@nextlyhq/eslint-plugin": "0.0.2-alpha.62",
-    "@nextlyhq/telemetry": "0.0.2-alpha.62",
-    "@nextlyhq/tsconfig": "0.0.2-alpha.62"
+    "@nextlyhq/eslint-config": "0.0.2-alpha.64",
+    "@nextlyhq/eslint-plugin": "0.0.2-alpha.64",
+    "@nextlyhq/telemetry": "0.0.2-alpha.64",
+    "@nextlyhq/tsconfig": "0.0.2-alpha.64"
   },
   "engines": {
     "node": "^20.19.0 || ^22.12.0 || >=24.0.0"

package/templates/base/.env.example

@@ -9,9 +9,15 @@ DATABASE_URL={{databaseUrl}}
 # Generate with: openssl rand -base64 32
 NEXTLY_SECRET=change-me-generate-a-secure-secret
 
-# Application URL
+# Where the Nextly app itself lives: the admin, the API, and the origin its
+# emails and preview links point at.
 NEXT_PUBLIC_APP_URL=http://localhost:3000
 
+# Where READERS find the public site. Used for canonical links, Open Graph
+# tags, the sitemap and RSS. Set it when the public site is served from a
+# different origin than the app above; otherwise the app's origin is used.
+# NEXT_PUBLIC_SITE_URL=https://example.com
+
 # Development diagnostics (opt-in)
 # Uncomment to add a _devDiagnostics field to error responses, carrying the
 # error's log context and the underlying cause, so a failure names itself while

package/templates/base/src/app/layout.tsx

@@ -2,6 +2,7 @@ import type { Metadata } from "next";
 import "@fontsource-variable/geist";
 import "@fontsource-variable/geist-mono";
 import "./globals.css";
+import { SITE_URL } from "@/lib/site-url";
 
 /**
  * The faces are imported as STYLESHEETS from packages in `node_modules`, rather
@@ -34,9 +35,7 @@ import "./globals.css";
  * `https://yourblog.com`). The localhost fallback keeps dev working.
  */
 export const metadata: Metadata = {
-  metadataBase: new URL(
-    process.env.NEXT_PUBLIC_SITE_URL ?? "http://localhost:3000"
-  ),
+  metadataBase: new URL(SITE_URL),
   title: { default: "Nextly", template: "%s — Nextly" },
   description: "A site built with Nextly.",
 };

package/templates/base/src/lib/site-url.ts

@@ -0,0 +1,55 @@
+/**
+ * The origin this site's absolute URLs are built from.
+ *
+ * Absolute URLs are needed in places that leave the browser's context —
+ * `metadataBase`, canonical links, Open Graph tags, the sitemap, RSS and
+ * JSON-LD. A relative path is meaningless in all of them, so something has to
+ * name the origin.
+ *
+ * ## Why two variables, in this order
+ *
+ * `NEXT_PUBLIC_SITE_URL` is where READERS find the site. `NEXT_PUBLIC_APP_URL`
+ * is where the Nextly app itself lives — the admin, the API, the origin its
+ * emails and preview links point at. They are usually the same host and are
+ * not the same question: a headless setup serves its public pages from one
+ * origin and runs the admin on another.
+ *
+ * So the public one wins when it is set, and the app's own origin is used when
+ * it is not. That second step matters more than it looks: the generated `.env`
+ * sets `NEXT_PUBLIC_APP_URL`, so without it a project that configured the only
+ * URL it was given would still publish `localhost` canonicals and OG tags to
+ * production — silently, because nothing about a wrong absolute URL fails at
+ * build time.
+ *
+ * ## The development fallback reads the port it is actually served on
+ *
+ * Not a hardcoded 3000. Next assigns `process.env.PORT` to the port it ends up
+ * listening on — after its own "port in use, using available port instead"
+ * fallback — so this follows `next dev -p 4000`, and follows Next onto a
+ * different port when 3000 is taken. A literal cannot do either, and the
+ * failure is quiet: pages render while every absolute URL points somewhere
+ * nothing is listening.
+ *
+ * `PORT` is a server-side value and is not inlined into client bundles, so a
+ * client component importing this reads the plain default. That is the same
+ * answer it would have had anyway, and client code should prefer
+ * `window.location.origin`, which is exact.
+ */
+const DEV_PORT = process.env.PORT ?? "3000";
+
+export const SITE_URL =
+  process.env.NEXT_PUBLIC_SITE_URL ??
+  process.env.NEXT_PUBLIC_APP_URL ??
+  `http://localhost:${DEV_PORT}`;
+
+/**
+ * Join a path onto {@link SITE_URL} without duplicating slashes.
+ *
+ * @param path - A root-relative path; a leading slash is optional
+ * @returns The absolute URL
+ */
+export function absoluteUrl(path = "/"): string {
+  const base = SITE_URL.replace(/\/$/, "");
+  const p = path.startsWith("/") ? path : `/${path}`;
+  return `${base}${p}`;
+}

package/templates/blank/src/app/(frontend)/page.tsx

@@ -1,6 +1,7 @@
 import Link from "next/link";
 
 import { ThemeToggle } from "@/components/ThemeToggle";
+import { SITE_URL } from "@/lib/site-url";
 
 /**
  * Blank-template landing page (public route via the (frontend) route group).
@@ -26,8 +27,7 @@ interface SetupStatus {
 
 async function fetchSetupStatus(): Promise<SetupStatus | null> {
   try {
-    const baseUrl = process.env.NEXT_PUBLIC_SITE_URL ?? "http://localhost:3000";
-    const res = await fetch(`${baseUrl}/api/auth/setup-status`, {
+    const res = await fetch(`${SITE_URL}/api/auth/setup-status`, {
       cache: "no-store",
     });
     if (!res.ok) return null;

package/templates/blank/src/app/layout.tsx

@@ -3,6 +3,7 @@ import "@fontsource-variable/inter";
 import "@fontsource-variable/jetbrains-mono";
 
 import "./globals.css";
+import { SITE_URL } from "@/lib/site-url";
 
 /**
  * The faces are imported as STYLESHEETS from packages in `node_modules`, rather
@@ -37,9 +38,7 @@ import "./globals.css";
  * blank-template pages can use relative OG image URLs without breaking.
  */
 export const metadata: Metadata = {
-  metadataBase: new URL(
-    process.env.NEXT_PUBLIC_SITE_URL ?? "http://localhost:3000"
-  ),
+  metadataBase: new URL(SITE_URL),
   title: { default: "Nextly", template: "%s — Nextly" },
   description: "A Nextly project.",
 };