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

package/dist/index.mjs

@@ -1,5 +1,5 @@
 import { createRequire } from 'module';
-export { createNextly } from './chunk-MP4HG5TY.mjs';
+export { createNextly } from './chunk-APDKXW5L.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.51",
+  "version": "0.0.2-alpha.52",
   "description": "CLI to scaffold Nextly in your Next.js project",
   "license": "MIT",
   "type": "module",
@@ -42,9 +42,9 @@
     "typescript": "^5.9.3",
     "vite-tsconfig-paths": "^5.1.4",
     "vitest": "^4.1.0",
-    "@nextlyhq/eslint-config": "0.0.2-alpha.51",
-    "@nextlyhq/tsconfig": "0.0.2-alpha.51",
-    "@nextlyhq/telemetry": "0.0.2-alpha.51"
+    "@nextlyhq/eslint-config": "0.0.2-alpha.52",
+    "@nextlyhq/tsconfig": "0.0.2-alpha.52",
+    "@nextlyhq/telemetry": "0.0.2-alpha.52"
   },
   "engines": {
     "node": ">=20.0.0"

package/templates/base/.env.example

@@ -12,5 +12,16 @@ NEXTLY_SECRET=change-me-generate-a-secure-secret
 # Application URL
 NEXT_PUBLIC_APP_URL=http://localhost:3000
 
+# 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
+# you build instead of only in the server log.
+#
+# Left commented on purpose. It is the SECOND of two independent signals — the
+# first is NODE_ENV — 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
+
 # Storage Configuration
 {{storageEnvVars}}