@chipmobilesdk/rn-notification 0.5.0 → 0.7.0

package/CHANGELOG.md

@@ -1,5 +1,189 @@
 # @chipmobilesdk/rn-notification
 
+## 0.7.0
+
+### Minor Changes
+
+- Every peer range has an upper bound, and no package declares a peer it does not use. ([#21](https://github.com/operationd8979/chip-mobile-sdk/pull/21))
+
+  A peer range is now a caret, a tilde or an explicit `<`, except for `react` and
+  `react-native`: an app brings exactly one of each, so a floor is the only useful thing
+  to say about them. Every other peer is a library the app installs beside us, and an
+  open `>=` was a promise about versions nobody had run — mmkv 3→4 lost entitlements and
+  pending purchases exactly that way.
+
+  **Four of the new ceilings exclude a version that is already published**, so an app
+  that took the open range at its word may now see a peer warning. The new bound is the
+  major this release is tested against, which is the thing the old range failed to say:
+
+  | Peer | Was | Now | Published above the ceiling |
+  |---|---|---|---|
+  | `react-native-app-auth` (rn-auth) | `>=8` | `^8.0.0` | 9.0.0 |
+  | `react-native-keychain` (rn-auth) | `>=10` | `^10.0.0` | 11.0.0 |
+  | `@op-engineering/op-sqlite` (rn-local-db) | `>=17.1.0` | `^17.1.0` | 18.x, 19.x |
+  | `@react-native-firebase/messaging` (rn-notification) | `>=26.0.0` | `^26.0.0` | 27.x |
+
+  The others — `react-native-vision-camera` `^5.1.1`, `react-native-svg` `^15.15.0`,
+  `react-native-unistyles` `^3.2.0`, `@dr.pogodin/react-native-fs` `^2.39.2`,
+  `react-native-quick-crypto` `^1.0.0`, `react-native-notify-kit` `^10.5.0`,
+  `react-native-localize` `^3.7.0`, `react-native-mmkv` `^4.0.0` — exclude nothing that
+  exists today. rn-payment's mmkv range was already bounded (`>=4.0.0 <5`) and is now
+  written as the caret that means the same thing.
+
+  Peers nothing imports are gone. `rn-theme`, `rn-local-db` and `rn-notification` asked
+  for `react` without having a component or a hook between them; `rn-auth`, `rn-ai` and
+  `rn-i18n` asked for `react-native` without touching a React Native API (rn-auth reaches
+  both native modules through `lazyPeer`, rn-i18n formats on `Intl`); `rn-notification`
+  asked for `@react-native-firebase/app`, which messaging declares itself. `rn-ai` no
+  longer peers on `@chipmobilesdk/rn-auth` at all — it asks for a `TokenProvider`, a
+  two-method interface rn-auth's `auth` satisfies, so an app with its own token source
+  installs nothing extra. An app that enables push or signs in through rn-auth installs
+  the same packages as before; it is the manifest that stopped overstating.
+
+  `react-native-localize` is declared optional, which is what the code already did: the
+  time-zone reader goes through `lazyPeer` and falls back to `Intl` without it. The
+  `peerDependenciesMeta` entries that said `optional: false` are gone — that is npm's
+  default, and writing it down only invited the question of which peers were undecided.
+
+  `npm run check:manifests` now fails on an unbounded peer range, a peer nothing in
+  `src/` imports, and a `peerDependenciesMeta` entry for either, so the policy holds
+  without anyone remembering it.
+
+- Every package now ships built JavaScript with declaration files, instead of asking the
+  app to compile its TypeScript. ([#22](https://github.com/operationd8979/chip-mobile-sdk/pull/22))
+
+  Each tarball carries `lib/commonjs`, `lib/module` and `lib/typescript` (built with
+  `react-native-builder-bob`), and `src/` alongside them. What that changes for a
+  consumer:
+
+  - **Nothing to add to `transformIgnorePatterns`.** `require` resolves to the CommonJS
+    build, so an app's Jest loads this package without being told to transform it. That
+    was the one thing every consuming app had to know about us (DEP-04).
+  - **Typechecking reads our `.d.ts`** rather than compiling our source under our
+    `tsconfig`. A consumer's stricter — or looser — settings no longer meet our code.
+  - **`import` resolves to ESM**, so a bundler can tree-shake what it does not use.
+
+  No exported name changed, and no subpath moved: `.`, `./testing`, `./push`,
+  `./advanced`, `./app-auth`, `./keychain` and rn-core's twelve subpaths resolve exactly
+  as before, each now with its own declarations for both module systems. publint and
+  `attw --profile node16` pass on all twelve packages, which they could not before.
+
+  Inside the monorepo nothing changed either, and that is deliberate: every subpath also
+  declares a private `chipmobilesdk-source` condition pointing at its TypeScript, and
+  Metro, Jest and `tsc` here ask for that condition first. The demo app bundles 371
+  modules straight from `packages/*/src`, so editing a package still changes the app with
+  no build step, and coverage is still measured on the source. The condition is named for
+  this organization rather than using the conventional `source` because third-party
+  packages declare that one too — `@dr.pogodin/react-native-fs` does — and asking for it
+  pulled their sources into our stricter compile.
+
+  `npm run build:packages` builds everything, `prepack` rebuilds before any `npm pack`,
+  and `lib/` is git-ignored: the published bytes are produced by the release, never
+  committed. `npm run check:manifests` now fails a package whose `main`, `module`,
+  `types`, `source` condition, `files`, build script or `prepack` do not match this shape.
+
+### Patch Changes
+
+- Each package's public API and its weight are now recorded in the repository, so a change
+  to either is reviewed rather than discovered. ([#23](https://github.com/operationd8979/chip-mobile-sdk/pull/23))
+
+  `packages/<pkg>/etc/*.api.md` is an api-extractor report per entrypoint — twenty-seven
+  of them, generated from the declarations the package publishes and committed. A renamed
+  type, a widened union, one more optional field: all of it shows up in a pull request's
+  diff. `npm run check:api` fails when a report is out of date and `npm run api:update`
+  rewrites them.
+
+  A report that moves now needs a **minor or major** changeset for that package.
+  `check:changesets` enforces it, because the report is generated from what the package
+  publishes, and a patch release that moves the public surface is how a consumer's build
+  breaks on `npm update`. A report added for the first time is a baseline, not a change.
+  `./testing` deliberately has no report: test doubles are not a surface a release is
+  gated on.
+
+  `npm run check:size` holds every entrypoint to a budget in `.size-limit.json`, measured
+  on the ESM build with peers and rn-core treated as external — they are what an app
+  installs beside us, not our weight. Each budget started at today's measurement plus five
+  per cent, so growth becomes a decision someone makes instead of a drift nobody sees. The
+  current figures run from 500 B (`rn-core/lazy`) to 19 kB (rn-notification).
+
+  No behaviour or API changed in this release; the entry is here so the changelog records
+  when the reports and the budgets began.
+- Updated dependencies ([#22](https://github.com/operationd8979/chip-mobile-sdk/pull/22), [#23](https://github.com/operationd8979/chip-mobile-sdk/pull/23)):
+  - @chipmobilesdk/rn-core@0.2.0
+
+## 0.6.0
+
+### Minor Changes
+
+- `createNotifications(config, deps?)` assembles the whole package in one call. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
+  - It returns the scheduler, reconciler, recurrence, permissions, channels, interactions
+    and snapshot, wired over one engine, one state store and the one redacting
+    diagnostic emitter, plus `onInteraction`, `runMaintenance`, `canScheduleExactly` and
+    `dispose`. The engine, store, clock and time zone default to the real ones and can
+    be injected.
+  - `canScheduleExactly` follows the exact-alarm permission the package last read,
+    instead of each app passing its own callback (often `() => true`).
+  - Automatic maintenance has its standard steps registered: re-anchoring after a
+    time-zone change and the permission re-read, plus recurrence window refresh when you
+    pass `recurrenceRules`.
+  - The individual factories stay exported from the root, and are also available from
+    the new `@chipmobilesdk/rn-notification/advanced` entrypoint for apps that wire the
+    package themselves.
+  - Push: `getAvailability()` no longer fetches a token (which registered the device
+    with FCM, and APNs on iOS, just to answer the question). The new
+    `gate.handleBackground(raw)` runs a background payload through the same
+    normalization and persisted deduplication as a foreground one. Several
+    `onTokenChange` subscriptions no longer leak each other, and `dispose()` releases
+    them all.
+  - The README starts from `createNotifications`; its quick start is checked against a
+    type-checked example in the tests.
+
+- Fewer reads across the native bridge, storage written per collection, and one
+  pending budget for the whole app. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
+  - A reconcile, a group or owner cancel, and a tone apply each read the pending set
+    (or the channel list) once per pass instead of once per operation. Reconciling 100
+    changes now makes at most two full reads of the trigger list; it used to make one
+    or more per change. Scheduling one notification asks for identifiers only where the
+    engine can list them (`pendingIds`, optional on the engine port).
+  - Persisted state is stored under one key per collection. Recording a push
+    deduplication entry writes the dedup ledger alone, where every update used to
+    serialize the whole record. A record written by an earlier version is migrated on
+    first load.
+  - The series and migration ledgers no longer evict live entries at their cap. Only
+    exhausted series and retired channels are dropped; if live entries alone exceed the
+    cap they are all kept and the new `STATE_CAP_EXCEEDED` diagnostic says so. Evicting a
+    live entry reset a series' count and made a migrated tone look new.
+  - Reconciliation budgets a domain against the platform ceiling minus what other
+    domains, series and direct schedules already hold. Two domains could previously
+    overflow iOS's 64 pending notifications together while each reported no truncation.
+
+- Three fixes: what a tone change cancels, background interactions, and permanent denial. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
+  - `channels.apply()` cancels a pending notification only when it is on a tone the
+    package applied earlier and the configuration no longer declares. It used to cancel
+    everything whose tone was not in the list passed to that call, which included
+    notifications scheduled by other code through the same engine.
+  - Taps, actions and dismissals that arrive while the app is in the background are
+    delivered. `registerBackgroundNotificationHandler` takes an optional `onInteraction`
+    callback and an optional `store`: a running app's `onInteraction` handlers get the
+    event with `appState: 'background'`; otherwise the callback does; with no callback, or
+    one that throws, the event is kept in the store and delivered on the next start.
+    Before, background actions such as "Taken" or "Snooze" never reached the app.
+  - `permanentlyDenied` is now reported: after one refused display request on iOS, two on
+    Android 13+, and `DISPLAY_PERMISSION_PERMANENT` is emitted. The count resets once the
+    permission is seen granted. After `requestExactAlarmPermission()` the package re-reads
+    the capability when the user returns from system settings and notifies
+    `onPermissionChange`.
+
+### Patch Changes
+
+- The notify-kit engine is split by platform. Android and iOS behaviour live in separate
+  strategy files chosen once when the engine is created, instead of about fifteen
+  `Platform.OS` branches in one 790-line file. `createNotifyKitEngine` accepts an optional
+  `platform` for testing one platform's behaviour. No behaviour change. ([#19](https://github.com/operationd8979/chip-mobile-sdk/pull/19))
+
 ## 0.5.0
 
 ### Minor Changes

package/README.md

@@ -17,6 +17,55 @@ Every notification feature re-solves the same problems, and most of them are dis
 - Display permission and exact-alarm permission are **different things**, asked separately, and a refusal must not break the user's actual work.
 - Android channels are **immutable once created** — changing one is a migration, not an assignment.
 
+## Quick start
+
+`createNotifications` assembles the whole package: scheduler, reconciler, recurrence,
+permissions, channels, interactions, a diagnostic snapshot, and automatic maintenance.
+It applies your tones, loads persisted state, and schedules exactly only while the
+exact-alarm permission allows it.
+
+<!-- quick-start -->
+```ts
+import { createNotifications } from '@chipmobilesdk/rn-notification';
+
+export async function setUpNotifications(navigate: (routing: unknown) => void) {
+	const notifications = await createNotifications({
+		tones: [
+			{
+				id: 'reminder',
+				name: 'Reminders',
+				urgency: 'high',
+				sound: { enabled: true },
+				vibration: true,
+				badge: true,
+				version: 1,
+			},
+		],
+	});
+
+	await notifications.permissions.requestDisplayPermission();
+
+	await notifications.scheduler.schedule({
+		id: 'task:42:due', // derived from your data, never random
+		content: { title: 'Pay the rent', body: 'Due today' },
+		tone: 'reminder',
+		moment: { at: Date.parse('2026-12-01T08:00:00') },
+		routing: { screen: 'task', taskId: '42' },
+	});
+
+	notifications.onInteraction(async event => {
+		if (event.kind === 'tap') navigate(event.routing);
+	});
+
+	return notifications;
+}
+```
+<!-- /quick-start -->
+
+The individual factories (`createScheduler`, `createReconciler`, `initialize`, the
+maintenance steps, ...) remain available, from the package root and from
+`@chipmobilesdk/rn-notification/advanced`, for an app that needs a different wiring.
+
 ## Installation
 
 ```sh
@@ -29,12 +78,14 @@ cd ios && pod install
 
 | Package | Required | Purpose |
 |---|---|---|
-| `react` >= 19, `react-native` >= 0.85 | yes | Host framework |
-| `react-native-notify-kit` >= 10.5.0 | yes | Local notification engine |
-| `react-native-mmkv` >= 4.0.0 | yes | Bounded persisted state |
-| `react-native-localize` >= 3.7.0 | yes | Platform time zone for re-anchoring |
-| `@react-native-firebase/app` >= 26.0.0 | **optional** | Push only — required *by* messaging |
-| `@react-native-firebase/messaging` >= 26.0.0 | **optional** | Push only |
+| `react-native` >= 0.85 | yes | Host platform. There is no `react` peer: this package has no component and no hook |
+| `react-native-notify-kit` `^10.5.0` | yes | Local notification engine |
+| `react-native-mmkv` `^4.0.0` | yes | Bounded persisted state |
+| `react-native-localize` `^3.7.0` | **optional** | Platform time zone for re-anchoring. Already reached through `lazyPeer`: without it the reader falls back to `Intl`, which React Native does not promise to update when the device zone changes |
+| `@react-native-firebase/messaging` `^26.0.0` | **optional** | Push only |
+
+`@react-native-firebase/app` is not a peer of this package — messaging declares it
+itself — but an app that enables push still has to install it, as the note below says.
 
 ### Enabling push (optional)
 
@@ -150,18 +201,25 @@ The package re-anchors wall-clock notifications when it notices the device zone
 | Applies `config.tones` (and any channel migration) during `initialize()` | `reconcile()` — the desired set |
 | Runs every step on `runtime.registry` when the app returns to the foreground — with the trigger `timeZoneChange` when the device zone moved meanwhile | |
 
-The steps themselves need inputs only your app has — the series rules it registered, the identifiers it expects, its permission module — so you register them once on `runtime.registry` after `initialize()`:
+`createNotifications` registers the standard steps for you: re-anchoring after a
+time-zone change, re-reading permissions, and — when you pass your recurrence rules —
+refreshing their windows. Steps that need inputs only your app has are added on
+`notifications.runtime.registry`:
 
 ```ts
-const { runtime } = await initialize(config, { engine, store });
-runtime.registry.register(createReAnchorStep({ engine, timeZone, resolveTone, canScheduleExactly }));
-runtime.registry.register(createWindowRefreshStep({ recurrence, registeredRules: () => myRules }));
-runtime.registry.register(createVerifyStep({ engine, expectedIds: () => myExpectedIds }));
-runtime.registry.register(createPermissionRefreshStep({ permissions }));
-// On teardown (tests, a sign-out that rebuilds the runtime):
-runtime.dispose();
+const notifications = await createNotifications(config, {
+  recurrenceRules: () => myRules, // the rules your app registered; the package never stores them
+});
+notifications.runtime.registry.register(
+  createVerifyStep({ engine: notifications.runtime.engine, expectedIds: () => myExpectedIds }),
+);
+// On teardown (tests, a sign-out that rebuilds everything):
+notifications.dispose();
 ```
 
+Wiring it yourself with `initialize()` and the step factories (from `./advanced`) still
+works; then registering the steps is yours.
+
 Before 0.4.0 nothing triggered these steps; they ran only when the app called `runMaintenance()` itself. A cycle that throws is reported as `MAINTENANCE_FAILED`, because nothing awaits it.
 
 **Reconciliation never runs on its own.** Only you know what your data implies; a package that guessed would cancel notifications it does not understand.
@@ -298,6 +356,13 @@ await permissions.openSettings('display');                  // per-permission
 
 Six states, never collapsed: `notAsked`, `granted`, `denied`, `permanentlyDenied`, `provisional`, `notRequired`.
 
+`permanentlyDenied` means the system will not show its prompt again, so offer Settings
+(`shouldOfferSettings(state)`). The platform itself only ever says `denied`; the package
+counts refusals — one on iOS, two on Android 13+ — and forgets them once the permission
+is seen granted. The exact-alarm capability is granted on a system settings screen, so
+`requestExactAlarmPermission()` answers with the state before the user chose; the real
+answer is re-read when they return to the app and reaches `onPermissionChange`.
+
 **Ask after intent, never on first launch.** A prompt at the wrong moment is a permanent denial.
 
 **A refusal never fails your operation.** The user's work completes; the lost capability is reported separately.
@@ -310,7 +375,26 @@ notifications.onInteraction(async event => {
 });
 ```
 
-One handler, identical shape in foreground, background, and cold start. Events that arrive before your handler registers are **buffered durably** — they survive process death, which is exactly what a cold-start tap is.
+One handler, identical shape in foreground, background, and cold start (`event.appState` says which).
+
+**Background actions need the module-scope handler.** The engine has one background
+handler per process, registered in `index.js`. Pass it your store and, optionally, a
+callback:
+
+```ts
+registerBackgroundNotificationHandler({
+  engine,
+  store: createMmkvStore(), // an interaction nobody handled is kept for the next start
+  onInteraction: async event => {
+    // Optional: handle "Taken" or "Snooze" right away, inside the background window.
+  },
+});
+```
+
+While the app is running, a background tap or action goes to your `onInteraction`
+handlers as usual. In a process started only for the event, it goes to the callback
+above; without one (or if it throws) it is kept in the store and delivered when the app
+next starts. Before 0.6.0 these events were dropped. Events that arrive before your handler registers are **buffered durably** — they survive process death, which is exactly what a cold-start tap is.
 
 Text the user typed into a reply action (`inputText`) is the exception: it is free text, so it is **never written to disk**. It is held in memory beside the buffer, so a handler that registers later in the same process still receives it; if the process dies first, the event is delivered without `inputText`.
 
@@ -342,6 +426,14 @@ Foreground pushes are **never auto-displayed** — presentation is your decision
 
 Local schedules take precedence over push for the same identifier. A server that wants to override sends `cancel` then `schedule`.
 
+## Channel changes and notifications already scheduled
+
+`channels.apply()` cancels a pending notification only when it sits on a tone this
+package applied earlier and the configuration no longer declares. Notifications
+scheduled by other code through the same engine, and tones the package has never
+applied, are left alone (0.6.0; before, anything not in the list passed to `apply()` was
+cancelled).
+
 ## What is persisted
 
 Six collections, in app-private, backup-excluded storage:
@@ -412,7 +504,7 @@ The state snapshot (`createSnapshot`) reports the pending set entry by entry, bu
 
 45 stable identifiers across validation, reconciliation, permissions, channels, interaction, push, state, and volume. Every one is reachable through the fault injector. See `ALL_DIAGNOSTIC_CODES`.
 
-Some are **reported outcomes, not failures** — the operation succeeded and something you should know happened alongside it: `TRUNCATED_OVER_CEILING`, `EXACT_ALARM_UNAVAILABLE`, `TARGET_MISSING`, `PENDING_SET_DISCREPANCY`, `BURST_THRESHOLD_EXCEEDED`, `PAYLOAD_VERSION_SKEW`, `PAYLOAD_DUPLICATE`, `STATE_CAP_EVICTED`, `STATE_CORRUPT_REBUILT`, `DND_BYPASS_UNAVAILABLE`, `TONE_LABELS_REFRESHED`, `REPEAT_ALERT_UNAVAILABLE`, `REPEAT_STOP_HANDLER_MISSING`. Use `isNonFailure(code)`.
+Some are **reported outcomes, not failures** — the operation succeeded and something you should know happened alongside it: `TRUNCATED_OVER_CEILING`, `EXACT_ALARM_UNAVAILABLE`, `TARGET_MISSING`, `PENDING_SET_DISCREPANCY`, `BURST_THRESHOLD_EXCEEDED`, `PAYLOAD_VERSION_SKEW`, `PAYLOAD_DUPLICATE`, `STATE_CAP_EVICTED`, `STATE_CAP_EXCEEDED`, `STATE_CORRUPT_REBUILT`, `DND_BYPASS_UNAVAILABLE`, `TONE_LABELS_REFRESHED`, `REPEAT_ALERT_UNAVAILABLE`, `REPEAT_STOP_HANDLER_MISSING`. Use `isNonFailure(code)`.
 
 ## License
 

package/lib/commonjs/advanced.js

@@ -0,0 +1,139 @@
+"use strict";
+
+Object.defineProperty(exports, "__esModule", {
+  value: true
+});
+Object.defineProperty(exports, "MaintenanceController", {
+  enumerable: true,
+  get: function () {
+    return _toggle.MaintenanceController;
+  }
+});
+Object.defineProperty(exports, "MaintenanceRegistry", {
+  enumerable: true,
+  get: function () {
+    return _cycle.MaintenanceRegistry;
+  }
+});
+Object.defineProperty(exports, "StateManager", {
+  enumerable: true,
+  get: function () {
+    return _record.StateManager;
+  }
+});
+Object.defineProperty(exports, "createBurstDetector", {
+  enumerable: true,
+  get: function () {
+    return _burst.createBurstDetector;
+  }
+});
+Object.defineProperty(exports, "createChannels", {
+  enumerable: true,
+  get: function () {
+    return _migrate.createChannels;
+  }
+});
+Object.defineProperty(exports, "createInteractions", {
+  enumerable: true,
+  get: function () {
+    return _index4.createInteractions;
+  }
+});
+Object.defineProperty(exports, "createMmkvStore", {
+  enumerable: true,
+  get: function () {
+    return _mmkvStore.createMmkvStore;
+  }
+});
+Object.defineProperty(exports, "createPermissionRefreshStep", {
+  enumerable: true,
+  get: function () {
+    return _permissionRefresh.createPermissionRefreshStep;
+  }
+});
+Object.defineProperty(exports, "createPermissions", {
+  enumerable: true,
+  get: function () {
+    return _index5.createPermissions;
+  }
+});
+Object.defineProperty(exports, "createPlatformTimeZoneReader", {
+  enumerable: true,
+  get: function () {
+    return _anchor.createPlatformTimeZoneReader;
+  }
+});
+Object.defineProperty(exports, "createReAnchorStep", {
+  enumerable: true,
+  get: function () {
+    return _reanchor.createReAnchorStep;
+  }
+});
+Object.defineProperty(exports, "createReconciler", {
+  enumerable: true,
+  get: function () {
+    return _index2.createReconciler;
+  }
+});
+Object.defineProperty(exports, "createRecurrence", {
+  enumerable: true,
+  get: function () {
+    return _index3.createRecurrence;
+  }
+});
+Object.defineProperty(exports, "createScheduler", {
+  enumerable: true,
+  get: function () {
+    return _index.createScheduler;
+  }
+});
+Object.defineProperty(exports, "createSnapshot", {
+  enumerable: true,
+  get: function () {
+    return _snapshot.createSnapshot;
+  }
+});
+Object.defineProperty(exports, "createToneResolver", {
+  enumerable: true,
+  get: function () {
+    return _toneMap.createToneResolver;
+  }
+});
+Object.defineProperty(exports, "createVerifyStep", {
+  enumerable: true,
+  get: function () {
+    return _verify.createVerifyStep;
+  }
+});
+Object.defineProperty(exports, "createWindowRefreshStep", {
+  enumerable: true,
+  get: function () {
+    return _windowRefresh.createWindowRefreshStep;
+  }
+});
+Object.defineProperty(exports, "initialize", {
+  enumerable: true,
+  get: function () {
+    return _initialize.initialize;
+  }
+});
+var _initialize = require("./initialize.js");
+var _index = require("./schedule/index.js");
+var _index2 = require("./reconcile/index.js");
+var _index3 = require("./recurrence/index.js");
+var _migrate = require("./channel/migrate.js");
+var _toneMap = require("./channel/tone-map.js");
+var _index4 = require("./interaction/index.js");
+var _snapshot = require("./diagnostics/snapshot.js");
+var _burst = require("./diagnostics/burst.js");
+var _index5 = require("./permission/index.js");
+var _permissionRefresh = require("./maintenance/permission-refresh.js");
+var _reanchor = require("./maintenance/reanchor.js");
+var _verify = require("./maintenance/verify.js");
+var _windowRefresh = require("./maintenance/window-refresh.js");
+var _toggle = require("./maintenance/toggle.js");
+var _cycle = require("./maintenance/cycle.js");
+var _record = require("./state/record.js");
+var _mmkvStore = require("./state/mmkv-store.js");
+var _anchor = require("./schedule/anchor.js");
+//# sourceMappingURL=advanced.js.map

package/lib/commonjs/advanced.js.map

@@ -0,0 +1 @@
+{"version":3,"names":["_initialize","require","_index","_index2","_index3","_migrate","_toneMap","_index4","_snapshot","_burst","_index5","_permissionRefresh","_reanchor","_verify","_windowRefresh","_toggle","_cycle","_record","_mmkvStore","_anchor"],"sourceRoot":"../../src","sources":["advanced.ts"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAOA,IAAAA,WAAA,GAAAC,OAAA;AAEA,IAAAC,MAAA,GAAAD,OAAA;AAEA,IAAAE,OAAA,GAAAF,OAAA;AAEA,IAAAG,OAAA,GAAAH,OAAA;AAEA,IAAAI,QAAA,GAAAJ,OAAA;AAEA,IAAAK,QAAA,GAAAL,OAAA;AACA,IAAAM,OAAA,GAAAN,OAAA;AAEA,IAAAO,SAAA,GAAAP,OAAA;AAEA,IAAAQ,MAAA,GAAAR,OAAA;AACA,IAAAS,OAAA,GAAAT,OAAA;AAEA,IAAAU,kBAAA,GAAAV,OAAA;AACA,IAAAW,SAAA,GAAAX,OAAA;AACA,IAAAY,OAAA,GAAAZ,OAAA;AACA,IAAAa,cAAA,GAAAb,OAAA;AACA,IAAAc,OAAA,GAAAd,OAAA;AACA,IAAAe,MAAA,GAAAf,OAAA;AAEA,IAAAgB,OAAA,GAAAhB,OAAA;AACA,IAAAiB,UAAA,GAAAjB,OAAA;AACA,IAAAkB,OAAA,GAAAlB,OAAA","ignoreList":[]}