@agntcms/next 0.3.0 → 0.3.1

package/dist/config.cjs

@@ -89,7 +89,6 @@ function withagntcms(nextConfig) {
   const pageExtensions = Array.isArray(userPageExtensions) ? userPageExtensions : [...defaultPageExtensions];
   return {
     ...nextConfig,
-    output: "standalone",
     pageExtensions
   };
 }

package/dist/config.d.cts

@@ -99,20 +99,17 @@ declare function defineConfig(config: AgentCmsConfig): ResolvedConfig;
 /**
  * Wrap a Next.js configuration object for agntcms.
  *
- * Sets `output: 'standalone'` so the production Docker build
- * (which copies `.next/standalone/`) works out of the box.
- *
- * Also injects a `pageExtensions` default: in dev we accept `.dev.ts` /
+ * Injects a `pageExtensions` default: in dev we accept `.dev.ts` /
  * `.dev.tsx` so dev-only routes (preview, admin, MCP) can be named
  * `route.dev.ts` and excluded from the production build automatically.
  * If the user already provided `pageExtensions`, theirs wins — the
  * convention is opt-in.
  *
- * In future versions this may also configure webpack aliases,
- * image optimization domains, or framework-level middleware.
+ * Exists as the stable wrapping point for future framework-level
+ * Next.js config (webpack aliases, image domains, middleware), so the
+ * template's call site does not need to change as the framework grows.
  */
 declare function withagntcms<T extends Record<string, unknown>>(nextConfig: T): T & {
-    output: 'standalone';
     pageExtensions: string[];
 };
 

package/dist/config.d.ts

@@ -99,20 +99,17 @@ declare function defineConfig(config: AgentCmsConfig): ResolvedConfig;
 /**
  * Wrap a Next.js configuration object for agntcms.
  *
- * Sets `output: 'standalone'` so the production Docker build
- * (which copies `.next/standalone/`) works out of the box.
- *
- * Also injects a `pageExtensions` default: in dev we accept `.dev.ts` /
+ * Injects a `pageExtensions` default: in dev we accept `.dev.ts` /
  * `.dev.tsx` so dev-only routes (preview, admin, MCP) can be named
  * `route.dev.ts` and excluded from the production build automatically.
  * If the user already provided `pageExtensions`, theirs wins — the
  * convention is opt-in.
  *
- * In future versions this may also configure webpack aliases,
- * image optimization domains, or framework-level middleware.
+ * Exists as the stable wrapping point for future framework-level
+ * Next.js config (webpack aliases, image domains, middleware), so the
+ * template's call site does not need to change as the framework grows.
  */
 declare function withagntcms<T extends Record<string, unknown>>(nextConfig: T): T & {
-    output: 'standalone';
     pageExtensions: string[];
 };
 

package/dist/config.mjs

@@ -44,7 +44,6 @@ function withagntcms(nextConfig) {
   const pageExtensions = Array.isArray(userPageExtensions) ? userPageExtensions : [...defaultPageExtensions];
   return {
     ...nextConfig,
-    output: "standalone",
     pageExtensions
   };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agntcms/next",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "agntcms runtime for Next.js: domain model, storage adapters, React components",
   "type": "module",
   "private": false,