edfcore 0.6.283 → 0.6.284

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.6.283";
+export declare const VERSION = "0.6.284";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.6.283';
+export const VERSION = '0.6.284';
 //# sourceMappingURL=constants.js.map

package/dist/text/describe.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"describe.d.ts","sourceRoot":"","sources":["../../src/text/describe.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAEH,iGAAiG;AACjG,wBAAgB,aAAa,CAAC,KAAK,EAAE,OAAO,GAAG,MAAM,CA2DpD;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,mBAAmB,CACjC,KAAK,EAAE;IAAE,QAAQ,CAAC,KAAK,CAAC,EAAE,OAAO,CAAC;IAAC,QAAQ,CAAC,KAAK,CAAC,EAAE,OAAO,CAAA;CAAE,GAAG,IAAI,GAAG,SAAS,GAC/E,MAAM,CAER"}
+{"version":3,"file":"describe.d.ts","sourceRoot":"","sources":["../../src/text/describe.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAEH,iGAAiG;AACjG,wBAAgB,aAAa,CAAC,KAAK,EAAE,OAAO,GAAG,MAAM,CAyEpD;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,mBAAmB,CACjC,KAAK,EAAE;IAAE,QAAQ,CAAC,KAAK,CAAC,EAAE,OAAO,CAAC;IAAC,QAAQ,CAAC,KAAK,CAAC,EAAE,OAAO,CAAA;CAAE,GAAG,IAAI,GAAG,SAAS,GAC/E,MAAM,CAER"}

package/dist/text/describe.js

@@ -34,9 +34,21 @@ export function describeValue(value) {
      * `decodeHeaderLatin1(buffer)` is a fetch result, and "an object" says nothing a reader can act
      * on. The tag, not `instanceof`: it is the same across realms, which is why `io/bytes.ts` uses it
      * too. Never the contents (0.6.116).
+     *
+     * The buffer half of that said `instanceof` anyway, which is the defect `io/bytes.ts` describes
+     * in those same words and fixed in its own guard in 0.3.20: an ArrayBuffer from another realm —
+     * an iframe, an Electron contextBridge, jsdom, a Node `vm` context — is a "real, fully usable
+     * ArrayBuffer", and `byteSource` accepts one. This module then could not name the thing the
+     * package next door takes, so `toPhysical(signal, thatBuffer)` was refused as "an object" while
+     * the identical buffer from this realm was refused as "ArrayBuffer". `SharedArrayBuffer` comes
+     * with it, because `byteSource` admits that tag too. Inlined rather than imported: layer 1
+     * cannot reach layer 5 (0.6.284).
      */
-    if (ArrayBuffer.isView(value) || value instanceof ArrayBuffer) {
-        return Object.prototype.toString.call(value).slice(8, -1);
+    const tag = Object.prototype.toString.call(value);
+    if (ArrayBuffer.isView(value) ||
+        tag === '[object ArrayBuffer]' ||
+        tag === '[object SharedArrayBuffer]') {
+        return tag.slice(8, -1);
     }
     /*
      * A REGEXP, by the same tag, for the same reason, in the place it is likeliest to turn up.
@@ -54,7 +66,7 @@ export function describeValue(value) {
      * `String(value)` is the source as written — `/EEG/i` — which is the whole of what a reader needs
      * to recognise it, and it is a pattern they typed rather than data read out of a file.
      */
-    if (Object.prototype.toString.call(value) === '[object RegExp]') {
+    if (tag === '[object RegExp]') {
         return `the RegExp ${String(value)}`;
     }
     /*

package/dist/text/describe.js.map

@@ -1 +1 @@
-{"version":3,"file":"describe.js","sourceRoot":"","sources":["../../src/text/describe.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAEH,iGAAiG;AACjG,MAAM,UAAU,aAAa,CAAC,KAAc;IAC1C,IAAI,OAAO,KAAK,KAAK,QAAQ;QAAE,OAAO,MAAM,CAAC,KAAK,CAAC,CAAC;IACpD,IAAI,OAAO,KAAK,KAAK,QAAQ;QAAE,OAAO,cAAc,KAAK,GAAG,CAAC;IAC7D,IAAI,OAAO,KAAK,KAAK,QAAQ;QAAE,OAAO,cAAc,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,EAAE,CAAC;IAC5E,IAAI,KAAK,KAAK,IAAI;QAAE,OAAO,MAAM,CAAC;IAClC,IAAI,KAAK,KAAK,SAAS;QAAE,OAAO,WAAW,CAAC;IAC5C;;;;;;OAMG;IACH,IAAI,WAAW,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,KAAK,YAAY,WAAW,EAAE,CAAC;QAC9D,OAAO,MAAM,CAAC,SAAS,CAAC,QAAQ,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,KAAK,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC;IAC5D,CAAC;IACD;;;;;;;;;;;;;;;OAeG;IACH,IAAI,MAAM,CAAC,SAAS,CAAC,QAAQ,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,iBAAiB,EAAE,CAAC;QAChE,OAAO,cAAc,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC;IACvC,CAAC;IACD;;;;;;;;;;;;;;;;;;;OAmBG;IACH,IAAI,OAAQ,KAA4B,CAAC,IAAI,KAAK,UAAU;QAAE,OAAO,mBAAmB,CAAC;IACzF,iGAAiG;IACjG,qFAAqF;IACrF,OAAO,OAAO,KAAK,KAAK,QAAQ,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,KAAK,OAAO,KAAK,EAAE,CAAC;AACvE,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,mBAAmB,CACjC,KAAgF;IAEhF,OAAO,YAAY,aAAa,CAAC,KAAK,EAAE,KAAK,CAAC,YAAY,aAAa,CAAC,KAAK,EAAE,KAAK,CAAC,IAAI,CAAC;AAC5F,CAAC"}
+{"version":3,"file":"describe.js","sourceRoot":"","sources":["../../src/text/describe.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAEH,iGAAiG;AACjG,MAAM,UAAU,aAAa,CAAC,KAAc;IAC1C,IAAI,OAAO,KAAK,KAAK,QAAQ;QAAE,OAAO,MAAM,CAAC,KAAK,CAAC,CAAC;IACpD,IAAI,OAAO,KAAK,KAAK,QAAQ;QAAE,OAAO,cAAc,KAAK,GAAG,CAAC;IAC7D,IAAI,OAAO,KAAK,KAAK,QAAQ;QAAE,OAAO,cAAc,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,EAAE,CAAC;IAC5E,IAAI,KAAK,KAAK,IAAI;QAAE,OAAO,MAAM,CAAC;IAClC,IAAI,KAAK,KAAK,SAAS;QAAE,OAAO,WAAW,CAAC;IAC5C;;;;;;;;;;;;;;;OAeG;IACH,MAAM,GAAG,GAAG,MAAM,CAAC,SAAS,CAAC,QAAQ,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;IAClD,IACE,WAAW,CAAC,MAAM,CAAC,KAAK,CAAC;QACzB,GAAG,KAAK,sBAAsB;QAC9B,GAAG,KAAK,4BAA4B,EACpC,CAAC;QACD,OAAO,GAAG,CAAC,KAAK,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC;IAC1B,CAAC;IACD;;;;;;;;;;;;;;;OAeG;IACH,IAAI,GAAG,KAAK,iBAAiB,EAAE,CAAC;QAC9B,OAAO,cAAc,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC;IACvC,CAAC;IACD;;;;;;;;;;;;;;;;;;;OAmBG;IACH,IAAI,OAAQ,KAA4B,CAAC,IAAI,KAAK,UAAU;QAAE,OAAO,mBAAmB,CAAC;IACzF,iGAAiG;IACjG,qFAAqF;IACrF,OAAO,OAAO,KAAK,KAAK,QAAQ,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,KAAK,OAAO,KAAK,EAAE,CAAC;AACvE,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,mBAAmB,CACjC,KAAgF;IAEhF,OAAO,YAAY,aAAa,CAAC,KAAK,EAAE,KAAK,CAAC,YAAY,aAAa,CAAC,KAAK,EAAE,KAAK,CAAC,IAAI,CAAC;AAC5F,CAAC"}

package/docs/CHANGELOG.md

@@ -6,6 +6,22 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.6.284
+
+- **Fixed** `describeValue` naming an `ArrayBuffer` from another realm "an object". `ArrayBuffer.isView`
+  is a brand check and so is realm-safe, but the buffer arm beside it said `instanceof ArrayBuffer`,
+  which is false for a buffer that crossed an iframe, an Electron contextBridge, jsdom or a Node `vm`
+  boundary.
+- `byteSource` takes such a buffer: `io/bytes.ts` has matched the built-in tag since 0.3.20, and its
+  docblock calls one "a real, fully usable ArrayBuffer from another realm". So the package accepted the
+  buffer at the door and could not name it at any of the roughly forty guards that read their subject
+  out of `describeValue` — `toPhysical(signal, buffer)` was refused as "the samples are an object"
+  while the identical buffer built in this realm was refused as "the samples are ArrayBuffer".
+- The describer's own docblock has stated the rule since 0.6.116 — "The tag, not `instanceof`: it is
+  the same across realms, which is why `io/bytes.ts` uses it too" — three lines above the branch that
+  did not follow it.
+- `SharedArrayBuffer` is named too, because `byteSource` admits that tag as well.
+
 ## 0.6.283
 
 - **Fixed** `trimToWindow` answering with an empty signal for a channel that declares no samples per

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.6.283",
+  "version": "0.6.284",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.6.283';
+export const VERSION = '0.6.284';

package/src/text/describe.ts

@@ -30,9 +30,23 @@ export function describeValue(value: unknown): string {
    * `decodeHeaderLatin1(buffer)` is a fetch result, and "an object" says nothing a reader can act
    * on. The tag, not `instanceof`: it is the same across realms, which is why `io/bytes.ts` uses it
    * too. Never the contents (0.6.116).
+   *
+   * The buffer half of that said `instanceof` anyway, which is the defect `io/bytes.ts` describes
+   * in those same words and fixed in its own guard in 0.3.20: an ArrayBuffer from another realm —
+   * an iframe, an Electron contextBridge, jsdom, a Node `vm` context — is a "real, fully usable
+   * ArrayBuffer", and `byteSource` accepts one. This module then could not name the thing the
+   * package next door takes, so `toPhysical(signal, thatBuffer)` was refused as "an object" while
+   * the identical buffer from this realm was refused as "ArrayBuffer". `SharedArrayBuffer` comes
+   * with it, because `byteSource` admits that tag too. Inlined rather than imported: layer 1
+   * cannot reach layer 5 (0.6.284).
    */
-  if (ArrayBuffer.isView(value) || value instanceof ArrayBuffer) {
-    return Object.prototype.toString.call(value).slice(8, -1);
+  const tag = Object.prototype.toString.call(value);
+  if (
+    ArrayBuffer.isView(value) ||
+    tag === '[object ArrayBuffer]' ||
+    tag === '[object SharedArrayBuffer]'
+  ) {
+    return tag.slice(8, -1);
   }
   /*
    * A REGEXP, by the same tag, for the same reason, in the place it is likeliest to turn up.
@@ -50,7 +64,7 @@ export function describeValue(value: unknown): string {
    * `String(value)` is the source as written — `/EEG/i` — which is the whole of what a reader needs
    * to recognise it, and it is a pattern they typed rather than data read out of a file.
    */
-  if (Object.prototype.toString.call(value) === '[object RegExp]') {
+  if (tag === '[object RegExp]') {
     return `the RegExp ${String(value)}`;
   }
   /*