@prodantix/sdk 0.6.0-beta.421 → 0.6.0-beta.425

package/dist/csp.d.cts

@@ -4,18 +4,14 @@
  *  anything that only resolves in the browser. A browser-only import here breaks
  *  the BUILD rather than the page, which is at least loud.
  *
- *  Moved out of `@bomdisoft/analytics` when that package was retired, and
- *  extended. The original emitted the analytics host alone, which was correct
- *  while events were the only thing the SDK sent. The messenger adds a websocket
- *  and a script, and a policy that is too narrow fails only in a visitor's
- *  browser console: nine sites permitted the analytics host and would have
- *  blocked the messenger with nothing on our side to show for it.
+ *  The messenger adds a websocket and a script to the analytics host, and a
+ *  policy that is too narrow fails only in a visitor's browser console, with
+ *  nothing on our side to show for it.
  *
  *  Every app that installs the SDK posts to `${host}/v1/…`, and a policy of
  *  `'self'` blocks that in every environment, not only locally: these hosts are
- *  different origins from the site in staging and production too. Analytics
- *  never worked from any of these apps until that was derived from the same env
- *  var the component reads.
+ *  different origins from the site in staging and production too, so the
+ *  sources derive from the same env var the component reads.
  */
 interface ProdantixHosts {
     /** Event ingest, e.g. `https://eu.api.prodantix.com`. */

package/dist/csp.d.ts

@@ -4,18 +4,14 @@
  *  anything that only resolves in the browser. A browser-only import here breaks
  *  the BUILD rather than the page, which is at least loud.
  *
- *  Moved out of `@bomdisoft/analytics` when that package was retired, and
- *  extended. The original emitted the analytics host alone, which was correct
- *  while events were the only thing the SDK sent. The messenger adds a websocket
- *  and a script, and a policy that is too narrow fails only in a visitor's
- *  browser console: nine sites permitted the analytics host and would have
- *  blocked the messenger with nothing on our side to show for it.
+ *  The messenger adds a websocket and a script to the analytics host, and a
+ *  policy that is too narrow fails only in a visitor's browser console, with
+ *  nothing on our side to show for it.
  *
  *  Every app that installs the SDK posts to `${host}/v1/…`, and a policy of
  *  `'self'` blocks that in every environment, not only locally: these hosts are
- *  different origins from the site in staging and production too. Analytics
- *  never worked from any of these apps until that was derived from the same env
- *  var the component reads.
+ *  different origins from the site in staging and production too, so the
+ *  sources derive from the same env var the component reads.
  */
 interface ProdantixHosts {
     /** Event ingest, e.g. `https://eu.api.prodantix.com`. */

package/package.json

@@ -63,5 +63,5 @@
   "sideEffects": false,
   "type": "module",
   "types": "./dist/index.d.ts",
-  "version": "0.6.0-beta.421"
+  "version": "0.6.0-beta.425"
 }