@buoy-gg/network 7.0.41 → 7.0.42

package/lib/commonjs/network/overrides/presets.js

@@ -1,70 +1 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-exports.draftFromEvent = draftFromEvent;
-exports.patternForUrl = patternForUrl;
-/**
- * Turning a captured request into a rule draft.
- *
- * Chrome's flow assumes a keyboard, a file tree and a second monitor. On a
- * phone the equivalent has to start from the request you're already looking at,
- * which is what this file is for — the editor never opens on a blank field.
- *
- * There used to be a list of one-tap presets here (Force 500, Empty list,
- * Offline…) rendered as chips. They're gone: the editor's outcome grid says the
- * same things in the same words, so keeping both meant two lists to maintain
- * and two places to look for the same choice.
- */
-
-/**
- * Turn a captured URL into a pattern that will match the request AGAIN.
- *
- * The query string is dropped and replaced with `*`, which is not a
- * simplification — it's the difference between a rule that works and one that
- * silently never fires. Plenty of clients cache-bust
- * (`?timestamp=1785783081234`), carry a request id, or page; pinning the exact
- * URL means the next call to the same endpoint doesn't match. Found exactly
- * that way: an "Offline" preset on a Pokémon request sat at 0 hits because the
- * app appends a timestamp to every call.
- *
- * The path stays exact, so this still means "this endpoint" and not "this
- * host" — and the editor shows the pattern, so narrowing it back down is one
- * edit away.
- */
-function patternForUrl(url) {
-  const query = url.indexOf("?");
-  return query === -1 ? url : `${url.slice(0, query)}*`;
-}
-
-/** Render a captured body as editable text. */
-function bodyToText(data) {
-  if (data == null) return "";
-  if (typeof data === "string") return data;
-  try {
-    return JSON.stringify(data, null, 2);
-  } catch {
-    return "";
-  }
-}
-
-/**
- * Prefill the rule editor from a captured request.
- *
- * Seeds the REAL response as the body so the common edit — change two fields of
- * a payload you just saw — starts from something true rather than from nothing.
- */
-function draftFromEvent(event) {
-  return {
-    enabled: true,
-    name: undefined,
-    urlPattern: patternForUrl(event.url),
-    methods: [String(event.method || "GET").toUpperCase()],
-    kind: "respond",
-    status: event.status && event.status >= 200 ? event.status : 200,
-    statusText: event.statusText,
-    body: bodyToText(event.responseData),
-    times: null
-  };
-}
+"use strict";Object.defineProperty(exports,"__esModule",{value:true});exports.draftFromEvent=draftFromEvent;exports.patternForUrl=patternForUrl;function patternForUrl(t){const r=t.indexOf("?");return r===-1?t:`${t.slice(0,r)}*`}function bodyToText(t){if(t==null)return"";if(typeof t==="string")return t;try{return JSON.stringify(t,null,2)}catch{return""}}function draftFromEvent(t){return{enabled:true,name:void 0,urlPattern:patternForUrl(t.url),methods:[String(t.method||"GET").toUpperCase()],kind:"respond",status:t.status&&t.status>=200?t.status:200,statusText:t.statusText,body:bodyToText(t.responseData),times:null}}

package/lib/commonjs/network/overrides/resolveOverride.js

@@ -1,158 +1 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-exports.findMatchingRule = findMatchingRule;
-exports.isSpent = isSpent;
-exports.resolveOverride = resolveOverride;
-exports.shouldApply = shouldApply;
-exports.toOutcome = toOutcome;
-var _matchRule = require("./matchRule");
-var _types = require("./types");
-/**
- * Decide whether a request is overridden — the whole decision, in one pure
- * function.
- *
- * Pure on purpose: this is the piece worth unit-testing, and it runs inside the
- * app's own `XMLHttpRequest.send()`, so it must be cheap, total, and incapable
- * of throwing. Everything that could surprise (defaults, clamping, content-type
- * inference) is resolved HERE, so `applyToXhr` never makes a decision — it just
- * performs the outcome.
- */
-
-/**
- * Traffic that must never be overridden, whatever the user's rules say.
- *
- * A `*` pattern is a completely reasonable thing for a developer to write
- * ("break everything and see what the app does"), and without this it would
- * also break Buoy's own licence checks — turning "I tested an error state" into
- * "the dev tools stopped working and I don't know why". Metro/debugger traffic
- * is already excluded upstream by `networkListener.shouldIgnoreUrl`.
- */
-const NEVER_OVERRIDE = [/(^|\.)keygen\.sh/i, /^https?:\/\/(www\.)?buoy\.gg\/api\/license(\/|$)/i];
-function isProtectedUrl(url) {
-  return NEVER_OVERRIDE.some(pattern => pattern.test(url));
-}
-
-/**
- * Guess a `content-type` when the rule didn't set one.
- *
- * Getting this wrong is not cosmetic: a client that trusts the header (axios's
- * default transform, any `response.json()` wrapper) will hand the app a string
- * where it expected an object, and the override looks broken rather than the
- * header looking wrong.
- */
-function inferContentType(body) {
-  const trimmed = body.trim();
-  if (trimmed === "") return "text/plain; charset=utf-8";
-  if (trimmed.startsWith("{") || trimmed.startsWith("[")) {
-    try {
-      JSON.parse(trimmed);
-      return "application/json";
-    } catch {
-      // Looks like JSON, isn't. Fall through — mislabelling it would be worse.
-    }
-  }
-  return "text/plain; charset=utf-8";
-}
-function hasHeader(headers, name) {
-  const wanted = name.toLowerCase();
-  return Object.keys(headers).some(key => key.toLowerCase() === wanted);
-}
-
-/** Normalize a matched rule into the exact instructions the interceptor needs. */
-function toOutcome(rule) {
-  const delayMs = Math.max(0, rule.delayMs ?? 0);
-  if (rule.kind === "delay") {
-    return {
-      kind: "delay",
-      rule,
-      delayMs
-    };
-  }
-  if (rule.kind === "fail") {
-    return {
-      kind: "fail",
-      rule,
-      delayMs,
-      failKind: rule.failKind ?? "network"
-    };
-  }
-  const body = rule.body ?? "";
-  const headers = {
-    ...(rule.headers ?? {})
-  };
-  if (!hasHeader(headers, "content-type")) {
-    headers["content-type"] = inferContentType(body);
-  }
-  return {
-    kind: "respond",
-    rule,
-    delayMs,
-    // Clamped, not rejected: whatwg-fetch's Response constructor THROWS outside
-    // [200, 599], which would crash the app's own fetch instead of overriding
-    // it. The editor constrains the input; this guarantees it.
-    status: Math.min(_types.STATUS_MAX, Math.max(_types.STATUS_MIN, rule.status ?? 200)),
-    statusText: rule.statusText ?? "",
-    headers,
-    body
-  };
-}
-
-/** A rule that has burned through its `times` budget no longer applies. */
-function isSpent(rule) {
-  return typeof rule.times === "number" && rule.hits >= rule.times;
-}
-
-/**
- * Is this rule in a phase where it should actually fire?
- *
- * Only `alternate` can answer no. It reads the CURRENT `seen` count, before
- * this match is recorded, so an untouched rule (`seen === 0`) lets the first
- * request through and overrides the second.
- */
-function shouldApply(rule) {
-  if (!rule.alternate) return true;
-  return rule.seen % 2 === 1;
-}
-
-/**
- * The first enabled rule whose pattern covers this request, phase ignored.
- *
- * Separate from `resolveOverride` because an alternating rule has to advance
- * its phase on the requests it deliberately skips — the caller needs the rule
- * back even when the answer is "not this time".
- */
-function findMatchingRule(url, method, rules) {
-  if (rules.length === 0) return null;
-  // Chrome skips OPTIONS too (`NetworkPersistenceManager.ts:953`). A faked
-  // preflight fails CORS in a way that looks nothing like the rule you wrote.
-  if (method.toUpperCase() === "OPTIONS") return null;
-  if (isProtectedUrl(url)) return null;
-  for (const rule of rules) {
-    if (!rule.enabled) continue;
-    if (isSpent(rule)) continue;
-    if (!(0, _matchRule.ruleMatches)(rule, url, method)) continue;
-    return rule;
-  }
-  return null;
-}
-
-/**
- * First ENABLED matching rule wins outright — no merging across rules.
- *
- * Chrome cascades header overrides from the most general path segment to the
- * most specific, but that only exists because its rules are directory-nested
- * files. A flat list with a cascade would be a rule whose effect you cannot see
- * by reading it, which is exactly the wrong trade on a phone screen.
- *
- * @param url    Full request URL, query string included.
- * @param method HTTP method as the caller sent it (case-insensitive).
- * @param rules  Ordered rule list; earlier entries win.
- */
-function resolveOverride(url, method, rules) {
-  const rule = findMatchingRule(url, method, rules);
-  if (!rule || !shouldApply(rule)) return null;
-  return toOutcome(rule);
-}
+"use strict";Object.defineProperty(exports,"__esModule",{value:true});exports.findMatchingRule=findMatchingRule;exports.isSpent=isSpent;exports.resolveOverride=resolveOverride;exports.shouldApply=shouldApply;exports.toOutcome=toOutcome;var _matchRule=require("./matchRule");var _types=require("./types");const NEVER_OVERRIDE=[/(^|\.)keygen\.sh/i,/^https?:\/\/(www\.)?buoy\.gg\/api\/license(\/|$)/i];function isProtectedUrl(t){return NEVER_OVERRIDE.some(e=>e.test(t))}function inferContentType(t){const e=t.trim();if(e==="")return"text/plain; charset=utf-8";if(e.startsWith("{")||e.startsWith("[")){try{JSON.parse(e);return"application/json"}catch{}}return"text/plain; charset=utf-8"}function hasHeader(t,e){const n=e.toLowerCase();return Object.keys(t).some(r=>r.toLowerCase()===n)}function toOutcome(t){const e=Math.max(0,t.delayMs??0);if(t.kind==="delay"){return{kind:"delay",rule:t,delayMs:e}}if(t.kind==="fail"){return{kind:"fail",rule:t,delayMs:e,failKind:t.failKind??"network"}}const n=t.body??"";const r={...t.headers??{}};if(!hasHeader(r,"content-type")){r["content-type"]=inferContentType(n)}return{kind:"respond",rule:t,delayMs:e,status:Math.min(_types.STATUS_MAX,Math.max(_types.STATUS_MIN,t.status??200)),statusText:t.statusText??"",headers:r,body:n}}function isSpent(t){return typeof t.times==="number"&&t.hits>=t.times}function shouldApply(t){if(!t.alternate)return true;return t.seen%2===1}function findMatchingRule(t,e,n,r){if(n.length===0)return null;if(e.toUpperCase()==="OPTIONS")return null;if(isProtectedUrl(t))return null;for(const i of n){if(!i.enabled)continue;if(isSpent(i))continue;if(!(0,_matchRule.ruleMatches)(i,t,e,r))continue;return i}return null}function resolveOverride(t,e,n,r){const i=findMatchingRule(t,e,n,r);if(!i||!shouldApply(i))return null;return toOutcome(i)}

package/lib/commonjs/network/overrides/types.js

@@ -1,90 +1 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-exports.STATUS_MIN = exports.STATUS_MAX = exports.MAX_RULES = exports.FREE_TIER_RULE_LIMIT = void 0;
-exports.markForOutcome = markForOutcome;
-var _sharedUi = require("@buoy-gg/shared-ui");
-/**
- * Network response overrides — the rule model.
- *
- * This is Buoy's answer to Chrome DevTools' "Local Overrides", reshaped for
- * mobile. Two deliberate differences from Chrome are worth knowing, because
- * they explain the whole shape of this file:
- *
- * 1. Chrome's rules ARE a directory tree — a body override is a file at
- *    `<host>/<path>`, header overrides live in per-directory `.headers` files,
- *    and its general→specific header cascade exists only to hang off that
- *    nesting. We have no filesystem, so rules are a flat ordered list and the
- *    FIRST enabled match wins outright. That's what Charles/Proxyman/MSW do,
- *    and it's what a developer can reason about on a phone screen.
- *
- * 2. Chrome CANNOT change a status code. `NetworkManager.ts` computes
- *    `responseCode = isBodyOverridden ? 200 : (responseStatusCode || 200)`, so
- *    overriding a body forces 200, and there is no latency or failure
- *    simulation at all. Chrome's feature is "serve different bytes". Forcing a
- *    500, a timeout or a 3s stall is the entire mobile use case, so `status`,
- *    `delayMs` and `kind: "fail"` below are the point of the exercise.
- */
-
-/**
- * What a rule does when it matches.
- *
- * - `respond` — synthesize a response. The request never leaves the device.
- * - `fail`    — synthesize a transport failure (offline / timeout). Also never
- *               leaves the device.
- * - `delay`   — let the real request run, just late. Pure latency injection.
- */
-
-/**
- * Which transport failure to fake.
- *
- * `network` surfaces the way a real offline request does — `fetch` rejects with
- * `TypeError: Network request failed`. This is also how you simulate "status 0":
- * you can't, via `respond`, because whatwg-fetch's `Response` constructor throws
- * a RangeError outside 200–599 (see STATUS_MIN/STATUS_MAX).
- */
-
-/**
- * Status codes a synthesized response may use.
- *
- * NOT an arbitrary product decision: React Native's `fetch` is the whatwg-fetch
- * polyfill, whose `Response` constructor throws
- * `RangeError: The status provided is outside the range [200, 599]`. A rule set
- * to 0 would therefore crash the app's own fetch call rather than override it.
- * Use `kind: "fail"` for connection-level failures.
- */
-const STATUS_MIN = exports.STATUS_MIN = 200;
-const STATUS_MAX = exports.STATUS_MAX = 599;
-
-/** Bounds the persisted list so a runaway UI can't fill storage. */
-const MAX_RULES = exports.MAX_RULES = 50;
-
-/**
- * @deprecated Read the live limit with `useLimit("network.overrideRules")` —
- * this only reports the FREE tier's value. Kept because it is part of the
- * package's public exports.
- */
-const FREE_TIER_RULE_LIMIT = exports.FREE_TIER_RULE_LIMIT = _sharedUi.TIER_LIMITS["network.overrideRules"].free;
-
-/**
- * Stamped onto the `NetworkEvent` a rule affected, so the list can badge the
- * row and the detail view can offer "edit / disable the rule that did this".
- */
-
-/**
- * A matched rule, normalized into exactly what the interceptor needs — defaults
- * resolved, status clamped, content-type inferred. Keeping normalization in the
- * resolver means `applyToXhr` never has to make a decision.
- */
-
-/** The marker recorded for an outcome. */
-function markForOutcome(outcome) {
-  return {
-    ruleId: outcome.rule.id,
-    ruleName: outcome.rule.name,
-    kind: outcome.kind,
-    delayMs: outcome.delayMs || undefined
-  };
-}
+"use strict";Object.defineProperty(exports,"__esModule",{value:true});exports.STATUS_MIN=exports.STATUS_MAX=exports.MAX_RULES=exports.FREE_TIER_RULE_LIMIT=void 0;exports.markForOutcome=markForOutcome;var _sharedUi=require("@buoy-gg/shared-ui");const STATUS_MIN=exports.STATUS_MIN=200;const STATUS_MAX=exports.STATUS_MAX=599;const MAX_RULES=exports.MAX_RULES=50;const FREE_TIER_RULE_LIMIT=exports.FREE_TIER_RULE_LIMIT=_sharedUi.TIER_LIMITS["network.overrideRules"].free;function markForOutcome(e){return{ruleId:e.rule.id,ruleName:e.rule.name,kind:e.kind,delayMs:e.delayMs||void 0}}

package/lib/commonjs/network/sync/networkBodyResolver.js

@@ -1,39 +1 @@
-"use strict";
-
-Object.defineProperty(exports, "__esModule", {
-  value: true
-});
-exports.NetworkBodyResolverProvider = NetworkBodyResolverProvider;
-exports.useNetworkBodyResolver = useNetworkBodyResolver;
-var _react = require("react");
-var _jsxRuntime = require("react/jsx-runtime");
-/**
- * The full request/response bodies for a single network event, fetched on
- * demand. Either field may be `null` when the event genuinely has no body.
- */
-
-/**
- * Resolves request/response bodies that were omitted from a synced snapshot.
- *
- * Large bodies (see `networkSyncAdapter`) are stripped from the list snapshot
- * so they aren't re-streamed every ~200ms; the detail view fetches them lazily
- * through this resolver when a request is opened.
- *
- * On the device this is never provided — bodies are always inline — so the
- * detail view simply falls back to the inline data. The desktop dashboard
- * provides a resolver that fetches the body over the devtool protocol.
- */
-
-const NetworkBodyResolverContext = /*#__PURE__*/(0, _react.createContext)(null);
-function NetworkBodyResolverProvider({
-  resolver,
-  children
-}) {
-  return /*#__PURE__*/(0, _jsxRuntime.jsx)(NetworkBodyResolverContext.Provider, {
-    value: resolver,
-    children: children
-  });
-}
-function useNetworkBodyResolver() {
-  return (0, _react.useContext)(NetworkBodyResolverContext);
-}
+"use strict";Object.defineProperty(exports,"__esModule",{value:true});exports.NetworkBodyResolverProvider=NetworkBodyResolverProvider;exports.useNetworkBodyResolver=useNetworkBodyResolver;var _react=require("react");var _jsxRuntime=require("react/jsx-runtime");const NetworkBodyResolverContext=(0,_react.createContext)(null);function NetworkBodyResolverProvider({resolver:e,children:r}){return(0,_jsxRuntime.jsx)(NetworkBodyResolverContext.Provider,{value:e,children:r})}function useNetworkBodyResolver(){return(0,_react.useContext)(NetworkBodyResolverContext)}