@heystack/otel 0.3.2 → 0.3.4

package/README.md

@@ -157,6 +157,8 @@ As belt-and-suspenders the exporter also drops any span whose HTTP target points
 
 ## Migration / versioning
 
+- **`0.3.4`** — **type-inference fix (Workers).** Restores `instrument()`'s ability to infer the handler's concrete `Env` type. In 0.3.3 the signature was `instrument<E = unknown, H extends WorkerHandler<E>>`, so `E` defaulted to `unknown` and was never recovered from the handler — under `strictFunctionTypes` a Worker typed `fetch(req, env: Env, ctx)` then failed to compile (`TS2345: 'Env' is not assignable to 'unknown'`) unless the caller passed `instrument<Env>(...)` explicitly. 0.3.4 infers `E` from the handler argument (`instrument<H extends WorkerHandler<any>>(...): Instrumented<EnvOf<H>, H>`), so a bare `instrument(handler, cfg)` type-checks again. Runtime behaviour is unchanged; no `0.3.3` consumer needs the explicit type arg after upgrading.
+- **`0.3.3`** — `/next` uses bare, exports-mapped dynamic imports so the OpenNext (Cloudflare Pages) build resolves the workers entry correctly (fixes a build break). Workers/Node paths unchanged.
 - **`0.3.2`** — runtime-correctness fixes:
   - **ContextManager registered (CRITICAL).** 0.3.1's `suppressTracing` was a no-op because no ContextManager was registered, so the exporter's ingest POST could still be re-traced into a feedback loop. 0.3.2 registers an `AsyncLocalStorageContextManager` (Node + workerd under `nodejs_compat`; sync stack-manager fallback otherwise) so suppression works — and as a bonus you get cross-`await` span parenting + per-request context isolation. **Workers now require `nodejs_compat`.** New dependency: `@opentelemetry/context-async-hooks`.
   - **Hostname-accurate self-span filter** (no sibling-domain false positives; `host:port` now matched; more host-only attrs covered).

package/dist/next.js

@@ -44,13 +44,23 @@ export async function registerHeystack(o) {
         // path (and a workers build must not bundle the node path) — the import is
         // runtime-selected per environment. `@vite-ignore` covers Vite/Rollup;
         // `webpackIgnore` covers Next/Turbopack/webpack.
+        //
+        // IMPORTANT: use the BARE package subpath ("@heystack/otel/workers"), NOT a
+        // relative "./workers.js". With the ignore hints the specifier is left as a
+        // literal runtime import; Next relocates this code into a server chunk and
+        // OpenNext's esbuild re-bundles it. A relative path would then resolve
+        // against the CHUNK dir (where no workers.js exists) and the build fails
+        // (issue: 0.3.2 broke OpenNext builds this way). A bare specifier resolves
+        // through Node's exports map / node_modules from anywhere, surviving both
+        // Next chunk relocation and OpenNext's re-bundle. The exports map points
+        // "./workers" → "./dist/workers.js" and "./node" → "./dist/node.js".
         const { initHeystackWorkers } = await import(
-        /* @vite-ignore */ /* webpackIgnore: true */ "./workers.js");
+        /* @vite-ignore */ /* webpackIgnore: true */ "@heystack/otel/workers");
         initHeystackWorkers({ apiKey, service: o.service, endpoint: o.endpoint });
     }
     else {
         const { initHeystack } = await import(
-        /* @vite-ignore */ /* webpackIgnore: true */ "./node.js");
+        /* @vite-ignore */ /* webpackIgnore: true */ "@heystack/otel/node");
         initHeystack({
             apiKey,
             service: o.service,

package/dist/workers.d.ts

@@ -253,5 +253,20 @@ type Instrumented<E, H> = Omit<H, "fetch" | "queue" | "scheduled"> & (H extends
 } ? {
     scheduled: (controller: ScheduledController, env: E, ctx: ExecutionContext) => Promise<void>;
 } : unknown);
-export declare function instrument<E = unknown, H extends WorkerHandler<E> = WorkerHandler<E>>(handler: H, config: WorkersConfig): Instrumented<E, H>;
+/**
+ * Recover a handler's concrete env type from whichever traced entrypoint it
+ * declares (`fetch`, else `queue`, else `scheduled`). This lets `instrument()`
+ * infer the env from the handler argument itself rather than requiring the
+ * caller to pass it explicitly — a Worker typed `fetch(req, env: Env, ctx)`
+ * type-checks with a bare `instrument(handler, cfg)` call. Falls back to
+ * `unknown` for a handler with no recognised entrypoint.
+ */
+type EnvOf<H> = H extends {
+    fetch: (req: Request, env: infer E, ctx: ExecutionContext) => unknown;
+} ? E : H extends {
+    queue: (batch: MessageBatch, env: infer E, ctx: ExecutionContext) => unknown;
+} ? E : H extends {
+    scheduled: (controller: ScheduledController, env: infer E, ctx: ExecutionContext) => unknown;
+} ? E : unknown;
+export declare function instrument<H extends WorkerHandler<any>>(handler: H, config: WorkersConfig): Instrumented<EnvOf<H>, H>;
 export type { Span };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@heystack/otel",
-  "version": "0.3.2",
+  "version": "0.3.4",
   "description": "Runtime-aware OpenTelemetry tracing that exports to Heystack (Node, Next.js, Workers).",
   "license": "MIT",
   "type": "module",
@@ -18,7 +18,9 @@
     "build": "tsc -p tsconfig.build.json",
     "test": "vitest run",
     "typecheck": "tsc --noEmit",
-    "prepublishOnly": "pnpm build"
+    "validate": "node scripts/validate-entries.mjs",
+    "check": "pnpm typecheck && pnpm build && pnpm validate && pnpm test",
+    "prepublishOnly": "pnpm build && pnpm validate"
   },
   "dependencies": {
     "@opentelemetry/api": "^1.9.0",