@djangocfg/nextjs 2.1.474 → 2.1.475

package/dist/index.mjs

@@ -14,7 +14,7 @@ var require_package = __commonJS({
   "package.json"(exports, module) {
     module.exports = {
       name: "@djangocfg/nextjs",
-      version: "2.1.474",
+      version: "2.1.475",
       description: "Next.js server utilities: sitemap, health, OG images, contact forms, navigation, config",
       keywords: [
         "nextjs",
@@ -1724,27 +1724,10 @@ function createBaseNextConfig(options = {}) {
       const userHeaders = options.headers ? await options.headers() : [];
       return [...headers, ...userHeaders];
     },
-    // Rewrites — first-party analytics ingest proxy, then user rewrites.
-    //
-    // @djangocfg/analytics POSTs to a RELATIVE /cfg/analytics/collect/ so the beacon
-    // stays same-origin (sendBeacon is unreliable cross-origin). On a split-domain
-    // deploy (Next on one host, Django on `apiUrl`) that same-origin path has no
-    // route here, so every beacon 404s and nothing is ingested — unless we proxy it.
-    // Same-domain and static builds keep apiUrl empty and need no proxy.
-    ...apiUrl && !isStaticBuild || options.rewrites ? {
-      async rewrites() {
-        const analyticsProxy = apiUrl && !isStaticBuild ? [{ source: "/cfg/analytics/:path*", destination: `${apiUrl}/cfg/analytics/:path*` }] : [];
-        const user = options.rewrites ? await options.rewrites() : [];
-        if (Array.isArray(user)) {
-          return { beforeFiles: analyticsProxy, afterFiles: user, fallback: [] };
-        }
-        return {
-          beforeFiles: [...analyticsProxy, ...user?.beforeFiles ?? []],
-          afterFiles: user?.afterFiles ?? [],
-          fallback: user?.fallback ?? []
-        };
-      }
-    } : {},
+    // Rewrites (user-provided only)
+    ...options.rewrites && {
+      rewrites: options.rewrites
+    },
     // Redirects for URL normalization
     // Fixes "Failed to construct 'URL': Invalid URL" error with double slashes
     async redirects() {