@hanzo/event 0.3.9 → 0.3.11

package/dist/{core-B1XEdWLd.d.cts → core-BZraSvcr.d.cts}

@@ -100,14 +100,29 @@ interface AnalyticsConfig {
     /** Bearer token provider for token-auth apps. Omit for cookie/session apps
      *  (the client then relies on same-origin credentials). */
     getToken?: () => string | undefined | null;
-    /** Publishable ingest key (pk_…). When set, the client authenticates to the ONE
-     *  front door `/v1/event` with this key instead of a bearer/cookie: it rides
-     *  Authorization: Bearer pk_… on fetch and ?ingest_key=pk_… on a headerless
-     *  page-unload beacon, so anonymous traffic is accepted and unload beacons work
-     *  without a bearer. The key is write-only (cannot read) and safe to ship in a
-     *  bundle; mint one per org via POST /v1/ingest/keys. This authenticates the
-     *  EVENT STREAM only — the error plane authenticates independently with `dsn`,
-     *  and one does not stand in for the other. */
+    /** Publishable ingest key (pk-…). When set, the client attributes writes to the
+     *  ONE front door `/v1/event` with this key instead of a bearer/cookie: it rides
+     *  Authorization: Bearer pk-… on fetch and ?ingest_key=pk-… on a headerless
+     *  page-unload beacon, so ANONYMOUS traffic is attributed and unload beacons work
+     *  without a bearer. The key is write-only — it attributes a write and never mints
+     *  a reading principal — so it is safe to ship in a bundle. Mint one per org with
+     *  POST /v1/keys {"type":"publishable"}.
+     *
+     *  Omit it and the client reads NEXT_PUBLIC_EVENT_INGEST_KEY from the inlined
+     *  build env, the same way `dsn` falls back — so a surface declares BOTH planes
+     *  in its build and neither needs code to switch on. That is the ONE spelling
+     *  the fleet already carries: KMS holds deploy/EVENT_INGEST_KEY, and each
+     *  Dockerfile takes EVENT_INGEST_KEY as a build-arg and re-exports it with the
+     *  NEXT_PUBLIC_ prefix that makes Next inline it.
+     *
+     *  A surface with no key at all still reports for whoever is SIGNED IN (the
+     *  session credential attributes them), and drops every logged-out visitor: the
+     *  door refuses an unattributable write rather than filing it where its owner
+     *  cannot read it. That failure is invisible from the page, which is why the key
+     *  belongs in the env next to the DSN and not in a checklist.
+     *
+     *  This attributes the EVENT STREAM only — the error plane authenticates
+     *  independently with `dsn`, and one does not stand in for the other. */
     ingestKey?: string;
     /** Max events buffered before an automatic flush. */
     batchSize?: number;

package/dist/{core-B1XEdWLd.d.ts → core-BZraSvcr.d.ts}

@@ -100,14 +100,29 @@ interface AnalyticsConfig {
     /** Bearer token provider for token-auth apps. Omit for cookie/session apps
      *  (the client then relies on same-origin credentials). */
     getToken?: () => string | undefined | null;
-    /** Publishable ingest key (pk_…). When set, the client authenticates to the ONE
-     *  front door `/v1/event` with this key instead of a bearer/cookie: it rides
-     *  Authorization: Bearer pk_… on fetch and ?ingest_key=pk_… on a headerless
-     *  page-unload beacon, so anonymous traffic is accepted and unload beacons work
-     *  without a bearer. The key is write-only (cannot read) and safe to ship in a
-     *  bundle; mint one per org via POST /v1/ingest/keys. This authenticates the
-     *  EVENT STREAM only — the error plane authenticates independently with `dsn`,
-     *  and one does not stand in for the other. */
+    /** Publishable ingest key (pk-…). When set, the client attributes writes to the
+     *  ONE front door `/v1/event` with this key instead of a bearer/cookie: it rides
+     *  Authorization: Bearer pk-… on fetch and ?ingest_key=pk-… on a headerless
+     *  page-unload beacon, so ANONYMOUS traffic is attributed and unload beacons work
+     *  without a bearer. The key is write-only — it attributes a write and never mints
+     *  a reading principal — so it is safe to ship in a bundle. Mint one per org with
+     *  POST /v1/keys {"type":"publishable"}.
+     *
+     *  Omit it and the client reads NEXT_PUBLIC_EVENT_INGEST_KEY from the inlined
+     *  build env, the same way `dsn` falls back — so a surface declares BOTH planes
+     *  in its build and neither needs code to switch on. That is the ONE spelling
+     *  the fleet already carries: KMS holds deploy/EVENT_INGEST_KEY, and each
+     *  Dockerfile takes EVENT_INGEST_KEY as a build-arg and re-exports it with the
+     *  NEXT_PUBLIC_ prefix that makes Next inline it.
+     *
+     *  A surface with no key at all still reports for whoever is SIGNED IN (the
+     *  session credential attributes them), and drops every logged-out visitor: the
+     *  door refuses an unattributable write rather than filing it where its owner
+     *  cannot read it. That failure is invisible from the page, which is why the key
+     *  belongs in the env next to the DSN and not in a checklist.
+     *
+     *  This attributes the EVENT STREAM only — the error plane authenticates
+     *  independently with `dsn`, and one does not stand in for the other. */
     ingestKey?: string;
     /** Max events buffered before an automatic flush. */
     batchSize?: number;

package/dist/index.cjs

@@ -246,7 +246,7 @@ function uuidv7Time(id) {
 }
 
 // src/version.ts
-var VERSION = "0.3.9";
+var VERSION = "0.3.11";
 
 // src/sentry.ts
 var MAX_FRAMES = 50;
@@ -616,7 +616,23 @@ var Analytics = class {
       flushIntervalMs: 5e3,
       enabled: true,
       captureErrors: true,
-      ...config
+      ...config,
+      // The publishable key resolves the SAME way the DSN below does: an explicit
+      // config wins, else the inlined build-time env.
+      //
+      // NEXT_PUBLIC_EVENT_INGEST_KEY is that env, and it is the name the fleet
+      // ALREADY carries end to end — KMS holds deploy/EVENT_INGEST_KEY, each
+      // Dockerfile takes it as the EVENT_INGEST_KEY build-arg and re-exports it
+      // with the NEXT_PUBLIC_ prefix Next needs to inline it. Reading anything
+      // else here would add a fourth spelling of one value.
+      //
+      // Without this the key was the one piece of wiring a surface could not
+      // declare the way it declares every other piece, so a surface that shipped
+      // without passing it in code sent its beacons unattributed — and an
+      // unattributed write is refused (401 ingest_key_required), which is silent
+      // in the page and invisible until you read the warehouse and find the host
+      // missing entirely.
+      ingestKey: config.ingestKey ?? readEnv("NEXT_PUBLIC_EVENT_INGEST_KEY")
     };
     this.transport = config.transport ?? new DefaultTransport();
     this.dsn = parseDsn(config.dsn ?? readEnvDsn() ?? dsnForProduct(this.cfg.product));