@djangocfg/api 2.1.470 → 2.1.472

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@djangocfg/api",
-  "version": "2.1.470",
+  "version": "2.1.472",
   "description": "Auto-generated TypeScript API client with React hooks, SWR integration, and Zod validation for Django REST Framework backends",
   "keywords": [
     "django",
@@ -84,7 +84,7 @@
     "zod": "^4.3.6"
   },
   "devDependencies": {
-    "@djangocfg/typescript-config": "^2.1.470",
+    "@djangocfg/typescript-config": "^2.1.472",
     "@testing-library/react": "^16.3.2",
     "@types/node": "^25.9.5",
     "@types/react": "19.2.15",

package/src/auth/utils/analytics.ts

@@ -1,9 +1,18 @@
 import { isDev } from "./env";
 /**
- * Analytics stub for @djangocfg/api/auth
- * Provides minimal analytics interface without external dependencies
+ * Auth analytics — a dependency-free SINK, not an implementation.
  *
- * If you need full analytics, install @djangocfg/layouts and use its Analytics module
+ * `@djangocfg/api` cannot depend on `@djangocfg/analytics`: analytics reads auth
+ * state (to attribute events to a signed-in user), so importing it here would
+ * close a dependency cycle. Instead this module owns the *interface* and lets a
+ * real implementation be injected at runtime — `@djangocfg/analytics` calls
+ * `setAnalyticsSink()` when its provider mounts.
+ *
+ * Before this, the object below was a hardcoded stub that console.logged in dev
+ * and did NOTHING in production. Every auth event it "tracked" —
+ * AUTH_LOGIN_SUCCESS, AUTH_OAUTH_FAIL, AUTH_SESSION_EXPIRED — was silently
+ * discarded. The events were fired, the calls looked right, and nothing ever
+ * arrived anywhere.
  */
 
 export enum AnalyticsEvent {
@@ -32,32 +41,46 @@ interface AnalyticsEventParams {
   [key: string]: any;
 }
 
+/** What an analytics implementation must provide to receive auth events. */
+export interface AnalyticsSink {
+  event(name: string, params?: Record<string, any>): void;
+  setUser(userId: string | null): void;
+}
+
+let sink: AnalyticsSink | null = null;
+
 /**
- * Minimal analytics implementation
- * Logs to console in development, silent in production
+ * Install the real analytics implementation.
+ *
+ * Called by `@djangocfg/analytics` when its provider mounts. Pass `null` to
+ * uninstall (on unmount), so a torn-down provider does not keep receiving events.
  */
+export function setAnalyticsSink(next: AnalyticsSink | null): void {
+  sink = next;
+}
+
 export const Analytics = {
-  /**
-   * Track an analytics event
-   */
+  /** Track an auth event. Delivered to the installed sink, if any. */
   event(eventName: AnalyticsEventType, params?: AnalyticsEventParams) {
+    if (sink) {
+      sink.event(eventName, params);
+      return;
+    }
+    // No sink installed: the app is not using @djangocfg/analytics. Say so in
+    // dev rather than pretending the event went somewhere.
     if (isDev) {
-      console.log('[Analytics]', eventName, params);
+      console.log('[Analytics:no-sink]', eventName, params);
     }
-
-    // You can extend this to send to your analytics service
-    // Example: window.gtag?.('event', eventName, params);
   },
 
-  /**
-   * Set user ID for tracking
-   */
-  setUser(userId: string) {
+  /** Attach the signed-in user. Pass null on logout. */
+  setUser(userId: string | null) {
+    if (sink) {
+      sink.setUser(userId);
+      return;
+    }
     if (isDev) {
-      console.log('[Analytics] Set user:', userId);
+      console.log('[Analytics:no-sink] Set user:', userId);
     }
-
-    // You can extend this to send to your analytics service
-    // Example: window.gtag?.('set', { user_id: userId });
   },
 };

package/src/auth/utils/index.ts

@@ -12,6 +12,10 @@ export {
   Analytics,
   AnalyticsEvent,
   AnalyticsCategory,
+  // Lets @djangocfg/analytics inject the real implementation without api having
+  // to depend on it (which would be a cycle — analytics reads auth state).
+  setAnalyticsSink,
+  type AnalyticsSink,
   type AnalyticsEventType,
   type AnalyticsCategoryType,
 } from './analytics';