edfcore 0.4.354 → 0.4.356

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.4.354";
+export declare const VERSION = "0.4.356";
 //# 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.4.354';
+export const VERSION = '0.4.356';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,30 @@ 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.4.356
+
+- **Added** an execution of the `resolveTimeWindow` example on `api-primitives.md`: a one-second
+  window from t = 2.5 on a file with one-second records, straddling records 2 and 3. The function
+  exists so the price of a window is auditable before a byte is read, and a reader planning a
+  viewport from that example is doing arithmetic that has to hold — including that two records are
+  paid for to get one second.
+- The three ways to get nothing back are checked as well, since returning `[]` rather than throwing
+  is what lets a caller loop over ranges with no special case: a non-positive duration, a window
+  outside the recording, and one inside a gap on an index that knows where the gaps are. The last
+  is paired with the case either side of it, so the emptiness is about the gap rather than about
+  the file. And a probed index over a file with gaps throws rather than guessing at onsets nobody
+  has read.
+
+## 0.4.355
+
+- **Fixed** a test of mine that could time out. The signature check added in 0.4.354 spawned `tsc`
+  inside an `it`, which takes a couple of seconds alone and rather more under a loaded suite —
+  past the default per-test timeout. It passed every run alone and failed the first time the whole
+  suite ran it.
+- Now compiled once at module scope, which is what `doc-snippets-compile.test.ts` next door
+  already does with its own compiler run. Collection time is not on a per-test clock, so the work
+  happens where it is not being timed, and nothing about the check weakens.
+
 ## 0.4.354
 
 - **Added** a compile check over every signature the reference pages print. Four pages open each

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.354",
+  "version": "0.4.356",
   "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.4.354';
+export const VERSION = '0.4.356';