create-nextly-app 0.0.2-alpha.50 → 0.0.2-alpha.52

package/dist/index.cjs

@@ -14316,6 +14316,22 @@ var import_fs_extra3 = __toESM(require_lib());
 function generateNextlySecret() {
   return crypto2__default.default.randomBytes(32).toString("base64");
 }
+function mentionsDiagnostics(env2) {
+  return /^[ \t]*(?:#[ \t]*)?(?:export[ \t]+)?NEXTLY_DEV_DIAGNOSTICS[ \t]*=/m.test(
+    env2
+  );
+}
+var DIAGNOSTICS_BLOCK = `# Development diagnostics (opt-in)
+# Uncomment to add a _devDiagnostics field to error responses, carrying the
+# log context of an error and the underlying cause, so a failure names itself
+# while you build instead of only in the server log.
+#
+# Left commented on purpose. It is the SECOND of two independent signals \u2014 the
+# first is NODE_ENV \u2014 and the second exists precisely because NODE_ENV is a
+# runtime value a deployment can carry by mistake. A default that ships in this
+# file would be true in exactly that case, which is the one it guards against.
+# NEXTLY_DEV_DIAGNOSTICS=1
+`;
 function getEnvTemplate(database) {
   return `# Nextly Configuration
 # Generated by create-nextly-app
@@ -14329,7 +14345,8 @@ NEXTLY_SECRET=${generateNextlySecret()}
 
 # Application URL
 NEXT_PUBLIC_APP_URL=http://localhost:3000
-`;
+
+${DIAGNOSTICS_BLOCK}`;
 }
 async function generateEnv(cwd, database) {
   const envPath = path14__default.default.join(cwd, ".env");
@@ -14342,6 +14359,10 @@ async function generateEnv(cwd, database) {
       await import_fs_extra3.default.appendFile(envPath, "\n" + envContent, "utf-8");
       return { created: false, updated: true };
     }
+    if (!mentionsDiagnostics(existingEnv)) {
+      await import_fs_extra3.default.appendFile(envPath, "\n" + DIAGNOSTICS_BLOCK, "utf-8");
+      return { created: false, updated: true };
+    }
     return { created: false, updated: false };
   }
   await import_fs_extra3.default.writeFile(envPath, envContent, "utf-8");