@flareapp/react-native 2.11.0 → 2.12.0

package/dist/index.cjs

@@ -5,13 +5,6 @@ let _flareapp_react_inject = require("@flareapp/react/inject");
 let react = require("react");
 
 //#region src/context/expo.ts
-/**
-* Lazy, synchronous Expo load. The `require(...)` calls MUST be direct string literals: Metro statically
-* collects only literal `require('pkg')` calls, treating those inside a try/catch as optional deps
-* (`allowOptionalDependencies` is on by default), so a missing package degrades to a caught throw not a
-* build error. Do NOT alias `require` to a local; that defeats the static collection and the module never
-* resolves even when installed. The `typeof require` guard keeps non-Metro/ESM envs (some test runners) safe.
-*/
 function loadExpoModules() {
 	const mods = {};
 	if (typeof require === "undefined") return mods;
@@ -23,14 +16,12 @@ function loadExpoModules() {
 	} catch {}
 	return mods;
 }
-/** Expo's `DeviceType` enum (UNKNOWN=0, PHONE=1, TABLET=2, DESKTOP=3, TV=4). */
 const DEVICE_TYPE_LABELS = {
 	1: "phone",
 	2: "tablet",
 	3: "desktop",
 	4: "tv"
 };
-/** Normalise the synchronous Expo constants into `DeviceInfo`. Only present (non-null) fields are set. */
 function expoToDeviceInfo(expo) {
 	const info = {};
 	const device = expo.device;
@@ -56,7 +47,6 @@ function expoToDeviceInfo(expo) {
 
 //#endregion
 //#region src/context/deviceInfo.ts
-/** Expo constants (resolved once) override the per-call RN-core `Platform`/`Dimensions` values. */
 var ReactNativeDeviceInfoProvider = class {
 	expoInfo;
 	constructor(expo = loadExpoModules()) {
@@ -87,7 +77,6 @@ var ReactNativeDeviceInfoProvider = class {
 		return info;
 	}
 };
-/** Android device model from `Platform.constants`, maker-prefixed (e.g. `Google Pixel 7`). iOS core exposes none. */
 function nativeModelName() {
 	if (react_native.Platform.OS !== "android") return;
 	const constants = react_native.Platform.constants;
@@ -105,15 +94,6 @@ function makeReactNativeContextCollector(expo = loadExpoModules()) {
 
 //#endregion
 //#region src/handlers/appStateFlush.ts
-/**
-* Flush the log buffer when the app backgrounds. Gate on `background` only: iOS fires `inactive` on every
-* transient interruption (app-switcher peek, Control Center, incoming call), so gating avoids flooding the
-* network. Mirrors the browser scheduler gating on `hidden`, not every blur. Delivery is best-effort (see
-* `ReactNativeFlushScheduler`).
-*
-* Returns an uninstaller that removes the listener via the subscription handle (modern RN API; do NOT use
-* the removed `AppState.removeEventListener`).
-*/
 function installAppStateFlush(getFlush) {
 	const subscription = react_native.AppState.addEventListener("change", (state) => {
 		if (state === "background") getFlush()?.();
@@ -123,7 +103,6 @@ function installAppStateFlush(getFlush) {
 
 //#endregion
 //#region src/devMode.ts
-/** True only in a React Native dev bundle. Safe (false) everywhere else. */
 function inDevMode() {
 	return typeof __DEV__ !== "undefined" && __DEV__ === true;
 }
@@ -133,16 +112,6 @@ function inDevMode() {
 function getErrorUtils() {
 	return globalThis.ErrorUtils;
 }
-/**
-* Wraps RN's `ErrorUtils` global handler: observe, do not swallow. The wrapper reports and then delegates
-* to the previous handler, so RN's own behaviour (red box in dev, crash in prod) is preserved.
-*
-* `onFatal` exists because a production fatal tears the app down while our report is still an async fetch
-* the OS kills, so a bare report rarely sends. With it, the previous handler is deferred until the
-* transport drains. Skipped in `__DEV__` so it does not fight the red box, and it only runs for the
-* first fatal, so a second one mid-flush hands straight over instead of starting a second shutdown.
-* Mirrors Sentry's RN SDK.
-*/
 function installGlobalErrorHandler(report, onFatal) {
 	const errorUtils = getErrorUtils();
 	if (!errorUtils) return () => {};
@@ -173,24 +142,15 @@ function installGlobalErrorHandler(report, onFatal) {
 
 //#endregion
 //#region src/handlers/rejectionTracking.ts
-/** An injected `null` means "engine absent" and must win over the live global, so this tests for
-*  `undefined` rather than falsiness. */
 function resolveHermes(deps) {
 	if (deps.hermes !== void 0) return deps.hermes;
 	return globalThis.HermesInternal;
 }
-/** Same `undefined`-not-falsy rule as `resolveHermes`. */
 function resolveRequire(deps) {
 	if (deps.requirePolyfill !== void 0) return deps.requirePolyfill;
 	if (typeof require === "undefined") return null;
 	return require;
 }
-/**
-* The rejection enabler for the active JS engine, null when neither is reachable. Order matters: on
-* Hermes the `promise` npm polyfill is not the runtime Promise, so its `rejection-tracking.enable()`
-* would hook unused objects and never fire. On JSC, RN does polyfill `global.Promise` with that package,
-* making it the real hook. Exported with injectable deps so the ordering is unit-testable.
-*/
 function resolveRejectionEnabler(deps = {}) {
 	const hermes = resolveHermes(deps);
 	if (hermes && typeof hermes.enablePromiseRejectionTracker === "function") return (options) => hermes.enablePromiseRejectionTracker(options);
@@ -202,16 +162,6 @@ function resolveRejectionEnabler(deps = {}) {
 	} catch {}
 	return null;
 }
-/**
-* Best-effort, engine-aware capture of unhandled rejections. RN routes these through the engine's tracker
-* rather than `window.onunhandledrejection`. With no engine hook reachable this is a no-op; uncaught
-* throws still arrive via ErrorUtils.
-*
-* Enabling REPLACES the engine's current callbacks, including RN's own dev warning, and neither engine
-* exposes a getter for the previous ones, so chaining is impossible. `onUnhandled` re-emits a
-* `console.warn` in dev to avoid swallowing that signal. For the same reason the uninstaller re-enables
-* with no-op callbacks: neither engine offers a clean disable.
-*/
 function installRejectionTracking(reporter, deps = {}) {
 	const enable = deps.enable !== void 0 ? deps.enable : resolveRejectionEnabler();
 	if (!enable) {
@@ -244,11 +194,6 @@ function installRejectionTracking(reporter, deps = {}) {
 
 //#endregion
 //#region src/ReactNativeFlushScheduler.ts
-/**
-* Passive: the AppState -> background trigger is wired separately in `Flare.install()`, to stay symmetric
-* with handler teardown. Flushes without `{ keepalive: true }` because RN's fetch runs over XMLHttpRequest
-* and does not reliably honour it, so a backgrounding flush is best-effort.
-*/
 var ReactNativeFlushScheduler = class {
 	flushFn = null;
 	register(flush) {
@@ -266,13 +211,11 @@ var ReactNativeFlushScheduler = class {
 //#endregion
 //#region src/Flare.ts
 const RN_SDK_NAME = "@flareapp/react-native";
-const RN_SDK_VERSION = "2.11.0";
-/** How long a fatal JS crash holds the app open to drain the transport before RN's default handler runs. */
+const RN_SDK_VERSION = "2.12.0";
 const FATAL_FLUSH_TIMEOUT_MS = 2e3;
 /**
-* The RN `Flare` singleton, exposed as `flare` from the package root. Uses `NullFileReader` because there
-* are no runtime snippets on a device (sourcemaps are a Metro follow-up) and `GlobalScopeProvider` because
-* RN has a single app scope.
+* The RN `Flare` singleton, exposed as `flare`. Uses `NullFileReader` (no runtime snippets on device) and
+* `GlobalScopeProvider` (RN has a single app scope).
 */
 var ReactNativeFlare = class extends _flareapp_core.Flare {
 	scheduler;
@@ -338,10 +281,9 @@ const flare = new ReactNativeFlare();
 //#endregion
 //#region src/FlareErrorBoundary.ts
 /**
-* React Native error boundary: a thin wrapper over `@flareapp/react`'s `/inject` boundary that injects the
-* RN `flare` singleton. `flare` is applied after `{...props}` so a consumer cannot override it. The
-* `as unknown as Flare` cast is needed because the prop is typed against `@flareapp/js/browser`'s `Flare`
-* (a superset); safe at runtime since the boundary only calls `reportSilently`, which RN inherits.
+* Wraps `@flareapp/react`'s `/inject` boundary with the RN `flare` singleton, applied after `{...props}`
+* so callers can't override it. The `Flare` cast is safe: the boundary only calls `reportSilently`, which
+* RN implements too.
 */
 function FlareErrorBoundary(props) {
 	return (0, react.createElement)(_flareapp_react_inject.FlareErrorBoundary, {

package/dist/index.d.cts

@@ -15,9 +15,8 @@ type RejectionDeps = {
 //#endregion
 //#region src/Flare.d.ts
 /**
- * The RN `Flare` singleton, exposed as `flare` from the package root. Uses `NullFileReader` because there
- * are no runtime snippets on a device (sourcemaps are a Metro follow-up) and `GlobalScopeProvider` because
- * RN has a single app scope.
+ * The RN `Flare` singleton, exposed as `flare`. Uses `NullFileReader` (no runtime snippets on device) and
+ * `GlobalScopeProvider` (RN has a single app scope).
  */
 declare class ReactNativeFlare extends Flare$1 {
   private readonly scheduler;
@@ -46,10 +45,9 @@ declare const flare: ReactNativeFlare;
 //#endregion
 //#region src/FlareErrorBoundary.d.ts
 /**
- * React Native error boundary: a thin wrapper over `@flareapp/react`'s `/inject` boundary that injects the
- * RN `flare` singleton. `flare` is applied after `{...props}` so a consumer cannot override it. The
- * `as unknown as Flare` cast is needed because the prop is typed against `@flareapp/js/browser`'s `Flare`
- * (a superset); safe at runtime since the boundary only calls `reportSilently`, which RN inherits.
+ * Wraps `@flareapp/react`'s `/inject` boundary with the RN `flare` singleton, applied after `{...props}`
+ * so callers can't override it. The `Flare` cast is safe: the boundary only calls `reportSilently`, which
+ * RN implements too.
  */
 declare function FlareErrorBoundary(props: Omit<FlareErrorBoundaryProps, 'flare'>): ReactElement;
 //#endregion

package/dist/index.d.mts

@@ -15,9 +15,8 @@ type RejectionDeps = {
 //#endregion
 //#region src/Flare.d.ts
 /**
- * The RN `Flare` singleton, exposed as `flare` from the package root. Uses `NullFileReader` because there
- * are no runtime snippets on a device (sourcemaps are a Metro follow-up) and `GlobalScopeProvider` because
- * RN has a single app scope.
+ * The RN `Flare` singleton, exposed as `flare`. Uses `NullFileReader` (no runtime snippets on device) and
+ * `GlobalScopeProvider` (RN has a single app scope).
  */
 declare class ReactNativeFlare extends Flare$1 {
   private readonly scheduler;
@@ -46,10 +45,9 @@ declare const flare: ReactNativeFlare;
 //#endregion
 //#region src/FlareErrorBoundary.d.ts
 /**
- * React Native error boundary: a thin wrapper over `@flareapp/react`'s `/inject` boundary that injects the
- * RN `flare` singleton. `flare` is applied after `{...props}` so a consumer cannot override it. The
- * `as unknown as Flare` cast is needed because the prop is typed against `@flareapp/js/browser`'s `Flare`
- * (a superset); safe at runtime since the boundary only calls `reportSilently`, which RN inherits.
+ * Wraps `@flareapp/react`'s `/inject` boundary with the RN `flare` singleton, applied after `{...props}`
+ * so callers can't override it. The `Flare` cast is safe: the boundary only calls `reportSilently`, which
+ * RN implements too.
  */
 declare function FlareErrorBoundary(props: Omit<FlareErrorBoundaryProps, 'flare'>): ReactElement;
 //#endregion

package/dist/index.mjs

@@ -9,13 +9,6 @@ var __require = /* @__PURE__ */ createRequire(import.meta.url);
 
 //#endregion
 //#region src/context/expo.ts
-/**
-* Lazy, synchronous Expo load. The `require(...)` calls MUST be direct string literals: Metro statically
-* collects only literal `require('pkg')` calls, treating those inside a try/catch as optional deps
-* (`allowOptionalDependencies` is on by default), so a missing package degrades to a caught throw not a
-* build error. Do NOT alias `require` to a local; that defeats the static collection and the module never
-* resolves even when installed. The `typeof require` guard keeps non-Metro/ESM envs (some test runners) safe.
-*/
 function loadExpoModules() {
 	const mods = {};
 	if (typeof __require === "undefined") return mods;
@@ -27,14 +20,12 @@ function loadExpoModules() {
 	} catch {}
 	return mods;
 }
-/** Expo's `DeviceType` enum (UNKNOWN=0, PHONE=1, TABLET=2, DESKTOP=3, TV=4). */
 const DEVICE_TYPE_LABELS = {
 	1: "phone",
 	2: "tablet",
 	3: "desktop",
 	4: "tv"
 };
-/** Normalise the synchronous Expo constants into `DeviceInfo`. Only present (non-null) fields are set. */
 function expoToDeviceInfo(expo) {
 	const info = {};
 	const device = expo.device;
@@ -60,7 +51,6 @@ function expoToDeviceInfo(expo) {
 
 //#endregion
 //#region src/context/deviceInfo.ts
-/** Expo constants (resolved once) override the per-call RN-core `Platform`/`Dimensions` values. */
 var ReactNativeDeviceInfoProvider = class {
 	expoInfo;
 	constructor(expo = loadExpoModules()) {
@@ -91,7 +81,6 @@ var ReactNativeDeviceInfoProvider = class {
 		return info;
 	}
 };
-/** Android device model from `Platform.constants`, maker-prefixed (e.g. `Google Pixel 7`). iOS core exposes none. */
 function nativeModelName() {
 	if (Platform.OS !== "android") return;
 	const constants = Platform.constants;
@@ -109,15 +98,6 @@ function makeReactNativeContextCollector(expo = loadExpoModules()) {
 
 //#endregion
 //#region src/handlers/appStateFlush.ts
-/**
-* Flush the log buffer when the app backgrounds. Gate on `background` only: iOS fires `inactive` on every
-* transient interruption (app-switcher peek, Control Center, incoming call), so gating avoids flooding the
-* network. Mirrors the browser scheduler gating on `hidden`, not every blur. Delivery is best-effort (see
-* `ReactNativeFlushScheduler`).
-*
-* Returns an uninstaller that removes the listener via the subscription handle (modern RN API; do NOT use
-* the removed `AppState.removeEventListener`).
-*/
 function installAppStateFlush(getFlush) {
 	const subscription = AppState.addEventListener("change", (state) => {
 		if (state === "background") getFlush()?.();
@@ -127,7 +107,6 @@ function installAppStateFlush(getFlush) {
 
 //#endregion
 //#region src/devMode.ts
-/** True only in a React Native dev bundle. Safe (false) everywhere else. */
 function inDevMode() {
 	return typeof __DEV__ !== "undefined" && __DEV__ === true;
 }
@@ -137,16 +116,6 @@ function inDevMode() {
 function getErrorUtils() {
 	return globalThis.ErrorUtils;
 }
-/**
-* Wraps RN's `ErrorUtils` global handler: observe, do not swallow. The wrapper reports and then delegates
-* to the previous handler, so RN's own behaviour (red box in dev, crash in prod) is preserved.
-*
-* `onFatal` exists because a production fatal tears the app down while our report is still an async fetch
-* the OS kills, so a bare report rarely sends. With it, the previous handler is deferred until the
-* transport drains. Skipped in `__DEV__` so it does not fight the red box, and it only runs for the
-* first fatal, so a second one mid-flush hands straight over instead of starting a second shutdown.
-* Mirrors Sentry's RN SDK.
-*/
 function installGlobalErrorHandler(report, onFatal) {
 	const errorUtils = getErrorUtils();
 	if (!errorUtils) return () => {};
@@ -177,24 +146,15 @@ function installGlobalErrorHandler(report, onFatal) {
 
 //#endregion
 //#region src/handlers/rejectionTracking.ts
-/** An injected `null` means "engine absent" and must win over the live global, so this tests for
-*  `undefined` rather than falsiness. */
 function resolveHermes(deps) {
 	if (deps.hermes !== void 0) return deps.hermes;
 	return globalThis.HermesInternal;
 }
-/** Same `undefined`-not-falsy rule as `resolveHermes`. */
 function resolveRequire(deps) {
 	if (deps.requirePolyfill !== void 0) return deps.requirePolyfill;
 	if (typeof __require === "undefined") return null;
 	return __require;
 }
-/**
-* The rejection enabler for the active JS engine, null when neither is reachable. Order matters: on
-* Hermes the `promise` npm polyfill is not the runtime Promise, so its `rejection-tracking.enable()`
-* would hook unused objects and never fire. On JSC, RN does polyfill `global.Promise` with that package,
-* making it the real hook. Exported with injectable deps so the ordering is unit-testable.
-*/
 function resolveRejectionEnabler(deps = {}) {
 	const hermes = resolveHermes(deps);
 	if (hermes && typeof hermes.enablePromiseRejectionTracker === "function") return (options) => hermes.enablePromiseRejectionTracker(options);
@@ -206,16 +166,6 @@ function resolveRejectionEnabler(deps = {}) {
 	} catch {}
 	return null;
 }
-/**
-* Best-effort, engine-aware capture of unhandled rejections. RN routes these through the engine's tracker
-* rather than `window.onunhandledrejection`. With no engine hook reachable this is a no-op; uncaught
-* throws still arrive via ErrorUtils.
-*
-* Enabling REPLACES the engine's current callbacks, including RN's own dev warning, and neither engine
-* exposes a getter for the previous ones, so chaining is impossible. `onUnhandled` re-emits a
-* `console.warn` in dev to avoid swallowing that signal. For the same reason the uninstaller re-enables
-* with no-op callbacks: neither engine offers a clean disable.
-*/
 function installRejectionTracking(reporter, deps = {}) {
 	const enable = deps.enable !== void 0 ? deps.enable : resolveRejectionEnabler();
 	if (!enable) {
@@ -248,11 +198,6 @@ function installRejectionTracking(reporter, deps = {}) {
 
 //#endregion
 //#region src/ReactNativeFlushScheduler.ts
-/**
-* Passive: the AppState -> background trigger is wired separately in `Flare.install()`, to stay symmetric
-* with handler teardown. Flushes without `{ keepalive: true }` because RN's fetch runs over XMLHttpRequest
-* and does not reliably honour it, so a backgrounding flush is best-effort.
-*/
 var ReactNativeFlushScheduler = class {
 	flushFn = null;
 	register(flush) {
@@ -270,13 +215,11 @@ var ReactNativeFlushScheduler = class {
 //#endregion
 //#region src/Flare.ts
 const RN_SDK_NAME = "@flareapp/react-native";
-const RN_SDK_VERSION = "2.11.0";
-/** How long a fatal JS crash holds the app open to drain the transport before RN's default handler runs. */
+const RN_SDK_VERSION = "2.12.0";
 const FATAL_FLUSH_TIMEOUT_MS = 2e3;
 /**
-* The RN `Flare` singleton, exposed as `flare` from the package root. Uses `NullFileReader` because there
-* are no runtime snippets on a device (sourcemaps are a Metro follow-up) and `GlobalScopeProvider` because
-* RN has a single app scope.
+* The RN `Flare` singleton, exposed as `flare`. Uses `NullFileReader` (no runtime snippets on device) and
+* `GlobalScopeProvider` (RN has a single app scope).
 */
 var ReactNativeFlare = class extends Flare$1 {
 	scheduler;
@@ -342,10 +285,9 @@ const flare = new ReactNativeFlare();
 //#endregion
 //#region src/FlareErrorBoundary.ts
 /**
-* React Native error boundary: a thin wrapper over `@flareapp/react`'s `/inject` boundary that injects the
-* RN `flare` singleton. `flare` is applied after `{...props}` so a consumer cannot override it. The
-* `as unknown as Flare` cast is needed because the prop is typed against `@flareapp/js/browser`'s `Flare`
-* (a superset); safe at runtime since the boundary only calls `reportSilently`, which RN inherits.
+* Wraps `@flareapp/react`'s `/inject` boundary with the RN `flare` singleton, applied after `{...props}`
+* so callers can't override it. The `Flare` cast is safe: the boundary only calls `reportSilently`, which
+* RN implements too.
 */
 function FlareErrorBoundary(props) {
 	return createElement(FlareErrorBoundary$1, {

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@flareapp/react-native",
-    "version": "2.11.0",
+    "version": "2.12.0",
     "description": "React Native SDK for flareapp.io",
     "homepage": "https://flareapp.io",
     "bugs": {
@@ -49,7 +49,7 @@
         "release": "release-it"
     },
     "dependencies": {
-        "@flareapp/core": "2.11.0"
+        "@flareapp/core": "2.12.0"
     },
     "peerDependencies": {
         "@flareapp/react": "^2.5.0",