@buoy-gg/network 7.0.18 → 7.0.20

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@buoy-gg/network",
-  "version": "7.0.18",
+  "version": "7.0.20",
   "description": "In-app network inspector for React Native — requests, responses, timing & errors live, with GraphQL operation parsing. Part of Buoy devtools.",
   "main": "lib/commonjs/index.js",
   "module": "lib/module/index.js",
@@ -26,7 +26,7 @@
   ],
   "sideEffects": false,
   "dependencies": {
-    "@buoy-gg/shared-ui": "^7.0.18"
+    "@buoy-gg/shared-ui": "^7.0.20"
   },
   "peerDependencies": {
     "react": "*",
@@ -54,7 +54,12 @@
           "sourceMaps": false
         }
       ],
-      "typescript"
+      [
+        "typescript",
+        {
+          "project": "tsconfig.build.json"
+        }
+      ]
     ]
   },
   "repository": {

package/lib/typescript/network/overrides/__tests__/applyToFetch.test.d.ts

@@ -1,16 +0,0 @@
-/**
- * Unit tests for the fetch-side synthesis.
- *
- * This layer exists because of a finding that only showed up on a real device:
- * Expo replaces `globalThis.fetch` with a NATIVE `expo/fetch` (see
- * `expo/src/winter/runtime.native.ts`), so those requests never construct an
- * XMLHttpRequest and an XHR-only override silently does nothing. Verified on
- * Expo SDK 56 / RN 0.85.3.
- *
- * Same self-contained harness as the other tests — see the run command in
- * `resolveOverride.test.ts`. Excluded from the publish build by
- * `tsconfig.build.json`.
- */
-declare function main(): Promise<void>;
-export { main as runApplyToFetchTests };
-//# sourceMappingURL=applyToFetch.test.d.ts.map

package/lib/typescript/network/overrides/__tests__/applyToFetch.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"applyToFetch.test.d.ts","sourceRoot":"","sources":["../../../../../src/network/overrides/__tests__/applyToFetch.test.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AA2KH,iBAAe,IAAI,kBAsBlB;AAaD,OAAO,EAAE,IAAI,IAAI,oBAAoB,EAAE,CAAC"}

package/lib/typescript/network/overrides/__tests__/applyToXhr.test.d.ts

@@ -1,19 +0,0 @@
-/**
- * Unit tests for the XHR response synthesis, against a faithful clone of React
- * Native's XMLHttpRequest state machine.
- *
- * WHY A CLONE RATHER THAN A MOCK: the interesting behaviour is not "did we set
- * some fields", it's whether RN's own `setReadyState` / `abort` branches then
- * do the right thing — which terminal event fires, and what `abort()` does when
- * `_sent` is or isn't claimed. A mock that just records calls would pass while
- * the real thing hung the app's fetch promise. `FakeRNXhr` below is transcribed
- * from `react-native/Libraries/Network/XMLHttpRequest.js` (verified identical on
- * RN 0.81.4 and 0.85.3), so these assertions are about real semantics.
- *
- * Same self-contained harness as the other tests — see the run command in
- * `resolveOverride.test.ts`. Excluded from the publish build by
- * `tsconfig.build.json`.
- */
-declare function main(): Promise<void>;
-export { main as runApplyToXhrTests };
-//# sourceMappingURL=applyToXhr.test.d.ts.map

package/lib/typescript/network/overrides/__tests__/applyToXhr.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"applyToXhr.test.d.ts","sourceRoot":"","sources":["../../../../../src/network/overrides/__tests__/applyToXhr.test.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AA2qBH,iBAAe,IAAI,kBAuBlB;AAaD,OAAO,EAAE,IAAI,IAAI,kBAAkB,EAAE,CAAC"}

package/lib/typescript/network/overrides/__tests__/resolveOverride.test.d.ts

@@ -1,22 +0,0 @@
-/**
- * Unit tests for the override matcher + resolver — the pure half of the
- * feature, and the half worth testing without a device.
- *
- * The glob cases mirror Chrome DevTools' own `escapeRegex` behaviour
- * (`NetworkPersistenceManager.ts:1051`), because these patterns are the same
- * syntax a developer already uses in Chrome's "Override headers" `applyTo`
- * field and must not quietly mean something different here.
- *
- * Same self-contained harness as the perf-monitor tests (no Jest wired up yet);
- * renames to Jest globals later. There is no `tsx` in this repo, so run it with
- * the esbuild that is already here, from the repo root:
- *
- *   node_modules/.bin/esbuild <this file> --bundle --platform=node \
- *     --format=cjs --outfile=/tmp/t.cjs && node /tmp/t.cjs
- *
- * `__tests__` is excluded from the publish build via `tsconfig.build.json`,
- * so this file ships nowhere — it's developer infrastructure.
- */
-declare function main(): Promise<void>;
-export { main as runResolveOverrideTests };
-//# sourceMappingURL=resolveOverride.test.d.ts.map

package/lib/typescript/network/overrides/__tests__/resolveOverride.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"resolveOverride.test.d.ts","sourceRoot":"","sources":["../../../../../src/network/overrides/__tests__/resolveOverride.test.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;GAkBG;AA0XH,iBAAe,IAAI,kBAuBlB;AAeD,OAAO,EAAE,IAAI,IAAI,uBAAuB,EAAE,CAAC"}

package/lib/typescript/network/sync/__tests__/networkSyncAdapter.test.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=networkSyncAdapter.test.d.ts.map

package/lib/typescript/network/sync/__tests__/networkSyncAdapter.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"networkSyncAdapter.test.d.ts","sourceRoot":"","sources":["../../../../../src/network/sync/__tests__/networkSyncAdapter.test.ts"],"names":[],"mappings":""}