edfcore 0.6.81 → 0.6.83

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

package/docs/CHANGELOG.md

@@ -6,6 +6,33 @@ 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.83
+
+- **Fixed** the landing page's gap example, whose two working lines both fail on the index it was
+  holding. `readWindow` across a gap THROWS on the probed index `openEdf` returns — two probes
+  cannot say where the hole is — and `precededByGap` is documented as "`undefined` on a probed
+  index, which is 'nobody looked' rather than 'no gap'".
+- That example is the page's whole argument for EDF+D support, and `discontinuous.md` opens by
+  demonstrating the same call failing before it reaches for `buildRecordIndex`. The landing page
+  showed the destination without the step. It now builds the index first, which is two lines.
+- `chunks[1]` is optional-chained as well, the class 0.6.78 fixed one sample above it. The test
+  runs the sequence against a file with a real hole and pins the old one throwing.
+
+## 0.6.82
+
+- **Fixed** the clock the inspector prints beside each event, which read
+  `onsetSecondsFromFirstRecord` and floored it. `format-annotations.ts` states the rule for the
+  library's own event list and why it is not fussiness: the seconds are "a float64 produced by
+  dividing an exact tick count by 10,000,000 … and an event list is exactly where someone reads a
+  number off the screen and types it into something else."
+- The inspector's table is that event list. It now divides `onsetTicksFromFirstRecord` in integers,
+  floors the way the library floors — so the printed time never names an instant later than the
+  event — and keeps the sign a negative onset carries, which EDF+ allows because a recording may
+  begin after its first annotation.
+- The test finds a tick count where the two routes disagree rather than assuming one exists: one
+  tick short of a whole second, at a scale where one tick is below the float's ulp, the float
+  route names the second AFTER the event.
+
 ## 0.6.81
 
 - **Fixed** the inspector deciding which events fall in the window it draws by comparing

package/package.json

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