lopata 0.18.4 → 0.19.0

package/src/module-cache.ts

@@ -1,58 +0,0 @@
-import path from 'node:path'
-
-interface ModuleRegistry {
-	registry: Map<unknown, unknown>
-}
-
-interface BunGlobal {
-	Loader?: ModuleRegistry
-}
-
-let warnedMissingRegistry = false
-
-/**
- * Invalidate the JavaScriptCore module registry for user-code files under
- * `baseDir`, excluding `node_modules`. This forces Bun to re-read and
- * re-evaluate every transitive dep on the next import.
- *
- * Why: lopata reloads the worker via `await import('<entry>?v=<ts>')`. That
- * query-string trick only invalidates the entry — Bun's module registry is
- * keyed by resolved specifier, so static imports inside the entry continue
- * to resolve to the originally cached transitive modules. Without this
- * call, edits to any file other than the entry itself silently no-op
- * across reloads (the watcher fires, `[lopata] Reloaded` prints, but the
- * active worker still references the old module graph).
- *
- * Caveats:
- *   - Uses `globalThis.Loader`, an undocumented JSC/Bun internal. If Bun
- *     ever renames or removes it, hot-reload regresses to the prior
- *     entry-only behavior — `tests/hmr-e2e.test.ts` "transitive dep
- *     change" cases will catch the regression.
- *   - `node_modules` paths are skipped so dependency imports stay cached
- *     across reloads (re-evaluating them every save would be slow and
- *     pointless — they don't change in a dev session).
- */
-export function invalidateUserModules(baseDir: string): void {
-	const loader = (globalThis as unknown as BunGlobal).Loader
-	if (!loader?.registry) {
-		if (!warnedMissingRegistry) {
-			warnedMissingRegistry = true
-			console.warn(
-				'[lopata] globalThis.Loader.registry not available — transitive hot-reload is disabled. '
-					+ 'Edits to files other than the worker entrypoint will require a manual restart.',
-			)
-		}
-		return
-	}
-
-	const prefix = path.resolve(baseDir) + path.sep
-	const nodeModulesSegment = `${path.sep}node_modules${path.sep}`
-	for (const key of [...loader.registry.keys()]) {
-		if (typeof key !== 'string') continue
-		// Strip query string (e.g. `?v=<ts>`) before comparing with disk paths.
-		const pathPart = key.split('?')[0] ?? key
-		if (!pathPart.startsWith(prefix)) continue
-		if (pathPart.includes(nodeModulesSegment)) continue
-		loader.registry.delete(key)
-	}
-}

package/src/tracing/global.d.ts

@@ -1,50 +0,0 @@
-/**
- * Lopata userland tracing API.
- *
- * Available on `globalThis.__lopata` when running under Lopata dev server.
- * In production (Cloudflare Workers) the global is `undefined` — wrap calls
- * in a thin helper that falls back to a no-op:
- *
- * ```ts
- * // app/lib/trace.ts
- * type TraceFn = <T>(name: string, fn: () => T | Promise<T>) => Promise<T>
- *
- * export const trace: TraceFn = (name, fn) =>
- *   globalThis.__lopata?.trace(name, fn) ?? fn()
- *
- * export const setAttribute = (key: string, value: unknown) =>
- *   globalThis.__lopata?.setAttribute(key, value)
- *
- * export const addEvent = (name: string, message?: string) =>
- *   globalThis.__lopata?.addEvent(name, message)
- * ```
- *
- * Add this file to your tsconfig types to get autocomplete:
- * ```json
- * { "compilerOptions": { "types": ["lopata/src/tracing/global"] } }
- * ```
- */
-
-interface LopataTracing {
-	/**
-	 * Create a traced span around `fn`. The span is visible in the Lopata
-	 * dashboard and becomes a child of the currently active span (if any).
-	 */
-	trace<T>(name: string, fn: () => T | Promise<T>): Promise<T>
-	/**
-	 * Create a traced span with custom attributes.
-	 */
-	trace<T>(name: string, attrs: Record<string, unknown>, fn: () => T | Promise<T>): Promise<T>
-
-	/**
-	 * Set an attribute on the currently active span.
-	 */
-	setAttribute(key: string, value: unknown): void
-
-	/**
-	 * Add an event (log entry) to the currently active span.
-	 */
-	addEvent(name: string, message?: string, attrs?: Record<string, unknown>): void
-}
-
-declare var __lopata: LopataTracing | undefined