@hanzo/event 0.3.38 → 0.3.40

package/dist/version.d.ts

@@ -1,2 +1,2 @@
-export declare const VERSION = "0.3.37";
+export declare const VERSION: string;
 //# sourceMappingURL=version.d.ts.map

package/dist/version.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"version.d.ts","sourceRoot":"","sources":["../src/version.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,OAAO,WAAW,CAAA"}
+{"version":3,"file":"version.d.ts","sourceRoot":"","sources":["../src/version.ts"],"names":[],"mappings":"AAWA,eAAO,MAAM,OAAO,EAAE,MAAgB,CAAA"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hanzo/event",
-  "version": "0.3.38",
+  "version": "0.3.40",
   "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/",
@@ -36,13 +36,6 @@
     "funnel",
     "hanzo"
   ],
-  "scripts": {
-    "build": "tsup && tsc --emitDeclarationOnly --declaration --outDir dist && node ../../scripts/dts.mjs",
-    "dev": "tsup --watch",
-    "test": "vitest run",
-    "typecheck": "tsc --noEmit -p tsconfig.json",
-    "clean": "rm -rf dist"
-  },
   "exports": {
     ".": {
       "import": {
@@ -74,14 +67,21 @@
     }
   },
   "devDependencies": {
-    "@types/node": "catalog:",
-    "@types/react": "catalog:",
-    "react": "catalog:",
-    "tsup": "catalog:",
-    "typescript": "catalog:",
-    "vitest": "catalog:"
+    "@types/node": "26.4.0",
+    "@types/react": "19.2.18",
+    "react": "19.2.8",
+    "tsup": "^8.5.1",
+    "typescript": "7.0.2",
+    "vitest": "^4.1.11"
   },
   "dependencies": {
-    "@hanzo/events": "catalog:"
+    "@hanzo/events": "0.2.2"
+  },
+  "scripts": {
+    "build": "tsup && tsc --emitDeclarationOnly --declaration --outDir dist && node ../../scripts/dts.mjs",
+    "dev": "tsup --watch",
+    "test": "vitest run",
+    "typecheck": "tsc --noEmit -p tsconfig.json",
+    "clean": "rm -rf dist"
   }
-}
+}

package/src/core.ts

@@ -699,6 +699,23 @@ function registry(): Map<string, Analytics> {
   return fresh
 }
 
+/** resetClients drops the page's clients, so the next `createAnalytics` for a
+ *  stream builds a fresh one.
+ *
+ *  A real page loads once and never needs this. A TEST RUNNER is what it exists
+ *  for: one document, many mounts, each meant to be its own page. The second one
+ *  gets a client that already counted this location, so its pageview is
+ *  correctly suppressed and the suite reads it as "nothing was emitted".
+ *
+ *  It is exported so a suite calls this instead of reaching for the slot itself.
+ *  A consumer that deletes the registry from its own code path takes the
+ *  guarantee with it: `<Provider/>` unmount/remount is not a new page, and the
+ *  fresh client it would get counts the same view again. */
+export function resetClients(): void {
+  const g = globalThis as unknown as Record<symbol, Map<string, Analytics> | undefined>
+  delete g[CLIENTS]
+}
+
 /** createAnalytics returns the client for a stream, building it on first ask.
  *  This is the ONE way to get a client: `new Analytics` bypasses the registry
  *  and is for tests and for a deliberately separate instance. */

package/src/index.ts

@@ -7,7 +7,14 @@
 //
 // React apps use the './react' entry for the provider + hooks + error boundary.
 
-export { Analytics, createAnalytics, VERSION, getCohort, getFirstTouch } from './core'
+export {
+  Analytics,
+  createAnalytics,
+  resetClients,
+  VERSION,
+  getCohort,
+  getFirstTouch,
+} from './core'
 export { parseDsn, buildSentryEvent, buildEnvelope, framesFromStack } from './sentry'
 export { uuidv7, uuidv7Time } from './uid'
 export { PRODUCT_PROJECT, dsnForProduct } from './dsn'

package/src/stream.test.ts

@@ -8,7 +8,7 @@
 // Authorization at all (401, ingest_key_required) — because the library asked
 // first and had no key. Both batches held a $pageview for the same page.
 import { describe, it, expect, beforeEach } from 'vitest'
-import { Analytics, createAnalytics } from './core'
+import { Analytics, createAnalytics, resetClients } from './core'
 import { PAGEVIEW } from './events'
 import type { Transport, WireEvent } from './types'
 
@@ -57,7 +57,7 @@ const app = () =>
 
 beforeEach(() => {
   tx = new FakeTransport()
-  delete (globalThis as unknown as Record<symbol, unknown>)[Symbol.for('hanzo.event.clients')]
+  resetClients() // each `it` is its own page load
   window.history.replaceState(null, '', '/pricing')
 })
 
@@ -135,6 +135,18 @@ describe('one stream, one client', () => {
     expect(createAnalytics({ product: 'site', host: HOST })).not.toBe(own)
   })
 
+  // The registry is page state, and only a new page may drop it. A consumer that
+  // dropped it from its own code — @hanzogui/telemetry did this on every provider
+  // unmount — gives the next caller a client that has never seen this page, and
+  // the view is counted a second time. So the reset is named here, where a test
+  // runner can say "new page" and nothing else can say it by accident.
+  it('drops the page clients on reset, and only then', () => {
+    const before = createAnalytics({ product: 'site', host: HOST })
+    expect(createAnalytics({ product: 'site', host: HOST })).toBe(before)
+    resetClients()
+    expect(createAnalytics({ product: 'site', host: HOST })).not.toBe(before)
+  })
+
   // The package publishes two entries and the react one carries its own copy of
   // this module, so on a page that imports both there are two module scopes. A
   // registry held in module scope is per-copy and would not dedupe the only case

package/src/version.ts

@@ -1,4 +1,12 @@
 // 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.37'
+//
+// Read from package.json rather than restated, because a version restated is a
+// version that drifts: 0.3.38 and 0.3.39 both shipped while this file still said
+// 0.3.37, so every event those builds sent named a library that was two releases
+// behind. `resolveJsonModule` inlines the literal at build time, and tsup shakes
+// the rest of the manifest out.
+import { version } from '../package.json'
+
+export const VERSION: string = version