@ultimat3/testing 22.3.4 → 22.3.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ultimat3/testing",
-  "version": "22.3.4",
+  "version": "22.3.6",
   "description": "Test harness: cloned template DBs per worker, frozen clock, sealed network, 6 test types",
   "license": "MIT",
   "type": "module",
@@ -35,16 +35,16 @@
     "test": "bun test"
   },
   "dependencies": {
-    "@ultimat3/cache": "22.3.4",
-    "@ultimat3/core": "22.3.4",
-    "@ultimat3/db": "22.3.4",
-    "@ultimat3/entity": "22.3.4",
-    "@ultimat3/i18n": "22.3.4",
-    "@ultimat3/jobs": "22.3.4",
-    "@ultimat3/mail": "22.3.4",
-    "@ultimat3/policy": "22.3.4",
-    "@ultimat3/query": "22.3.4",
-    "@ultimat3/realtime": "22.3.4",
-    "@ultimat3/time": "22.3.4"
+    "@ultimat3/cache": "22.3.6",
+    "@ultimat3/core": "22.3.6",
+    "@ultimat3/db": "22.3.6",
+    "@ultimat3/entity": "22.3.6",
+    "@ultimat3/i18n": "22.3.6",
+    "@ultimat3/jobs": "22.3.6",
+    "@ultimat3/mail": "22.3.6",
+    "@ultimat3/policy": "22.3.6",
+    "@ultimat3/query": "22.3.6",
+    "@ultimat3/realtime": "22.3.6",
+    "@ultimat3/time": "22.3.6"
   }
 }

package/src/index.ts

@@ -250,6 +250,7 @@ export {
   missingIslandFiles,
   normalizeIslandName,
 } from './island-states-resolve';
+export { ISOLATED_ENV, releasePluginsAfterIsolatedFile } from './isolated-plugins';
 export type { LiveConnection, LiveNodeHandle, LiveNodeOptions } from './live-node';
 export { createLiveNode } from './live-node';
 /**

package/src/isolated-plugins.ts

@@ -0,0 +1,37 @@
+// Frees each finished test file in an ISOLATED run. Bun 1.4.0 keeps every finished file's global
+// object — its module graph, PGlite heap and fakes — alive under `--isolate` (implied by
+// `--parallel`) once any `Bun.plugin` load/resolve handler is registered, and the framework
+// registers two in every file. `isolated-plugins.test.ts` measures it with real `bun test` runs.
+
+import { afterAll } from 'bun:test';
+
+/**
+ * Set by `x test` (`@ultimat3/cli`'s `test-shards.ts`) on every `bun test` it spawns in isolated
+ * mode. A preload cannot tell for itself: an isolated file sees the same argv, and a fresh process
+ * and env are exactly what isolation looks like from inside.
+ */
+export const ISOLATED_ENV = 'ULTIMATE_TEST_ISOLATED';
+
+/**
+ * `Bun.plugin.clearAll()` after each file, isolated runs only. Measured on notificado.co's unit
+ * suite (652 files, 18 workers): per-worker peak 2.1–2.3 GB → 1.0–1.5 GB, total ~30 GB → 18 GB. The
+ * next file's preload registers the plugins again, so every file still gets them.
+ *
+ * NEVER in a shared process: render's loader keeps an `installed` flag, so a cleared plugin is
+ * never re-registered and the next `.tsx` compiles with Bun's classic factory — `__xh is not
+ * defined`.
+ */
+export function releasePluginsAfterIsolatedFile(
+  env: Readonly<Record<string, string | undefined>> = Bun.env,
+  after: (hook: () => void) => void = afterAll,
+  plugin: { clearAll(): void } = Bun.plugin,
+): boolean {
+  if (env[ISOLATED_ENV] !== '1') return false;
+  after(() => clearPlugins(plugin));
+  return true;
+}
+
+/** Every `Bun.plugin` handler this process registered. The next file's preload registers them again. */
+export const clearPlugins = (plugin: { clearAll(): void } = Bun.plugin): void => {
+  plugin.clearAll();
+};

package/src/preload.ts

@@ -8,6 +8,7 @@
 import { installDeterminism } from './determinism';
 import { registerFrameworkFixtures } from './framework-fixtures';
 import './matchers';
+import { releasePluginsAfterIsolatedFile } from './isolated-plugins';
 import { installRegistryLeakGuard } from './registry-leak-guard';
 import { sealNetwork } from './sealed-network';
 
@@ -25,6 +26,10 @@ registerFrameworkFixtures();
 // fails a later file in another package, for a reason nothing in that file explains.
 installRegistryLeakGuard();
 
+// Isolated runs only (`x test` says so): Bun 1.4.0 keeps every finished file alive while a plugin
+// is registered. See `isolated-plugins.ts`.
+releasePluginsAfterIsolatedFile();
+
 // Opt-out exists for one case: a test that deliberately exercises a real integration in a job the
 // team runs on purpose. It is an env var, not an API, so it cannot be set from inside a test file.
 if (Bun.env['ULTIMATE_TEST_ALLOW_NET'] !== '1') sealNetwork();

package/src/registry-leak-guard.ts

@@ -111,8 +111,10 @@ let installed = false;
  * otherwise register the hooks twice and report every leak twice.
  *
  * Under `--isolate` each file gets its own module registry, so the guard judges that one file and
- * nothing carries across — which is correct, not a hole: with `--isolate` there is no cross-file
- * pollution to find, and a file that leaks is still reported against itself.
+ * no REGISTRY state carries across — which is correct, not a hole: a file that leaks is still
+ * reported against itself. MEMORY does carry across: on Bun 1.4.0 the plugin this registers keeps
+ * every finished file's global object alive for the life of the worker (~57 MB per file measured).
+ * `isolated-plugins.ts` clears the plugins after each isolated file.
  */
 export function installRegistryLeakGuard(): void {
   if (installed) return;