@plasius/analytics 1.3.1 → 1.3.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -1
- package/dist/index.cjs +422 -246
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +6 -1
- package/dist/index.d.ts +6 -1
- package/dist/index.js +110 -10
- package/dist/index.js.map +1 -1
- package/dist/metrics.cjs +121 -7
- package/dist/metrics.cjs.map +1 -1
- package/dist/metrics.js +92 -4
- package/dist/metrics.js.map +1 -1
- package/package.json +1 -1
- package/dist/chunk-5BHE32SK.cjs +0 -98
- package/dist/chunk-5BHE32SK.cjs.map +0 -1
- package/dist/chunk-OEVYIQET.js +0 -98
- package/dist/chunk-OEVYIQET.js.map +0 -1
package/README.md
CHANGED
|
@@ -1,5 +1,12 @@
|
|
|
1
1
|
# @plasius/analytics
|
|
2
2
|
|
|
3
|
+
For optional analytics, construct clients only after the host has obtained consent.
|
|
4
|
+
On withdrawal call `client.destroy({ discard: true })` to cancel pending transport
|
|
5
|
+
and remove its retained events and issue aggregates. Custom transports must honour
|
|
6
|
+
the provided `request.signal`. A late transport completion cannot recreate the
|
|
7
|
+
discarded queue; requests already received by a server cannot be recalled.
|
|
8
|
+
The semantic journey client's existing `destroy()` already aborts and discards.
|
|
9
|
+
|
|
3
10
|
[](https://www.npmjs.com/package/@plasius/analytics)
|
|
4
11
|
[](https://github.com/Plasius-LTD/analytics/actions/workflows/ci.yml)
|
|
5
12
|
[](https://codecov.io/gh/Plasius-LTD/analytics)
|
|
@@ -263,7 +270,9 @@ Lazy collectors should import `projectUsefulMetric` and
|
|
|
263
270
|
`USEFUL_METRIC_EVENT_DEFINITIONS` from `@plasius/analytics/metrics`. This standalone
|
|
264
271
|
ESM/CJS entry contains no React, collectors or transport. Existing root exports
|
|
265
272
|
remain compatible, but using the focused entry lets a bundler keep optional
|
|
266
|
-
metric code out of a host's
|
|
273
|
+
metric code out of a host's initial analytics graph, including when that host
|
|
274
|
+
loads the metric entry dynamically. The published entries are independent bundles
|
|
275
|
+
from one source, avoiding an eager shared metric chunk. The host must
|
|
267
276
|
still verify its real application bundle and own flag evaluation and transport.
|
|
268
277
|
|
|
269
278
|
Compose the fixed definitions into the host's semantic catalogue, then project
|