edfcore 0.6.60 → 0.6.62

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.60";
+export declare const VERSION = "0.6.62";
 //# 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.60';
+export const VERSION = '0.6.62';
 //# 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.62
+
+- **Fixed** `api-errors.md` publishing `EdfFormatErrorInit` a field short. It was written
+  `{ code, diagnostic?, field?, byteOffset?, signalIndex?, recordIndex?, cause? }`, and the
+  interface also has `collected?`.
+- `collected` is the one worth not losing: it carries the diagnostics the parse had already found
+  when one of them turned out to be fatal, which are often several that have nothing to do with
+  the fatal, and the fatal is frequently the least informative of the set. The same page
+  documents it two tables above, in the `EdfFormatError` field list — so the page explained the
+  field and then published an initialiser without it, which is the line a reader copies.
+- The guard is generic, like 0.6.55's for tables: any `` `Name`: `{ … }` `` spelling in the docs
+  whose `Name` is an exported interface must list that interface's fields, in declaration order.
+
+## 0.6.61
+
+- **Fixed** `api-errors.md` listing `name` among what a structured clone keeps. It keeps `message`,
+  `stack` and `cause`; `name` survives only for the seven built-in error types, and everything
+  else is normalised to `'Error'` — so every one of edfcore's seven classes arrives from a
+  `postMessage` named `Error`.
+- It is the one clause on that page a reader acts on. The section is about what to do when
+  `edfErrorKind` is gone, and two paragraphs later the page says `error.name` is the concrete
+  class's name, "`'EdfFormatError'` rather than `'Error'`". The obvious fallback in a worker is
+  therefore to branch on `name`, and on the receiving side that branch never matches.
+- The advice the section ends with is unchanged and was always right: send the discriminator
+  yourself. The test clones all six constructible classes through `structuredClone`, which is the
+  same algorithm `postMessage` uses, and checks a built-in keeps its name for contrast.
+
 ## 0.6.60
 
 - **Fixed** `header/signals.ts` saying that in `samplesPerRecord * bytesPerSample`, "Both numbers

package/package.json

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