@hanzo/event 0.3.27 → 0.3.28

package/hz.js

@@ -55,7 +55,7 @@
   }
 
   var LIB = 'hz.js'
-  var VERSION = '0.3.27'
+  var VERSION = '0.3.28'
   var host = (s.getAttribute('data-host') || 'https://api.hanzo.ai').replace(/\/+$/, '')
   var product = s.getAttribute('data-product') || location.hostname
   var capture = s.getAttribute('data-capture') !== '0'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hanzo/event",
-  "version": "0.3.27",
+  "version": "0.3.28",
   "description": "Hanzo Event — the ONE telemetry client. Emits pageview/event/identify/group to the Hanzo Cloud event stream (POST /v1/event), AND reports errors to Sentry as real Sentry envelopes — the error plane needs a DSN, without one nothing reaches Sentry. First-touch attribution, beacon-on-unload, auto error capture, client-side secret/PII scrubbing, a shared event + goal vocabulary. Subsumes @sentry.",
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",

package/src/core.ts

@@ -699,7 +699,14 @@ function registry(): Map<string, Analytics> {
  *  This is the ONE way to get a client: `new Analytics` bypasses the registry
  *  and is for tests and for a deliberately separate instance. */
 export function createAnalytics(config: AnalyticsConfig): Analytics {
-  if (!isBrowser()) return new Analytics(config)
+  // A disabled client emits nothing, so it can double nothing and does not take
+  // the stream. Callers reach their answer at different moments — a provider
+  // whose ownership resolves in an effect renders once saying `false` before it
+  // has decided anything — and the client built in that moment must not become
+  // the one the page keeps. Registering it would silence the page, and adopting
+  // `enabled` from a later caller would let one surface overrule another's
+  // reading of consent. Neither: it is simply not the stream's client.
+  if (!isBrowser() || config.enabled === false) return new Analytics(config)
   const key = (config.host ?? DEFAULT_HOST) + '\0' + config.product
   const clients = registry()
   const existing = clients.get(key)

package/src/stream.test.ts

@@ -95,6 +95,32 @@ describe('one stream, one client', () => {
     expect(tx.sent[0].ingestKey).toBe(KEY)
   })
 
+  // A provider whose ownership resolves in an effect renders once saying
+  // `enabled: false` and then again saying true. Measured on hanzo.ai: the
+  // library's first render built a disabled client, and a registry that kept it
+  // handed that one to the app too — the page went silent, which is worse than
+  // the double it replaced.
+  it('does not let a disabled client take the stream', () => {
+    const off = createAnalytics({ product: 'site', host: HOST, enabled: false })
+    const on = createAnalytics({ product: 'site', host: HOST, transport: tx, flushIntervalMs: 999999 })
+    expect(on).not.toBe(off)
+    on.pageview('/pricing')
+    on.flush()
+    expect(tx.pageviews).toHaveLength(1)
+    expect(createAnalytics({ product: 'site', host: HOST, getToken: () => KEY })).toBe(on)
+  })
+
+  it('gives every disabled caller its own inert client', () => {
+    const a = createAnalytics({ product: 'site', host: HOST, enabled: false, transport: tx })
+    const b = createAnalytics({ product: 'site', host: HOST, enabled: false, transport: tx })
+    expect(a).not.toBe(b)
+    a.pageview('/pricing')
+    b.pageview('/pricing')
+    a.flush()
+    b.flush()
+    expect(tx.sent).toHaveLength(0)
+  })
+
   it('keeps separate streams separate', () => {
     expect(createAnalytics({ product: 'chat', host: HOST })).not.toBe(
       createAnalytics({ product: 'site', host: HOST }),

package/src/version.ts

@@ -1,4 +1,4 @@
 // The library version, stamped on every event (`libraryVersion`) and on the
 // Sentry `sdk` block. It lives alone so `sentry.ts` can read it without importing
 // `core.ts` — core imports sentry, so the reverse would be an import cycle.
-export const VERSION = '0.3.27'
+export const VERSION = '0.3.28'