edfcore 0.6.60 → 0.6.61

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
109
109
  readonly reserved: 224;
110
110
  };
111
111
  /** Published package version. Kept in sync with package.json by a test. */
112
- export declare const VERSION = "0.6.60";
112
+ export declare const VERSION = "0.6.61";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.6.60';
82
+ export const VERSION = '0.6.61';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,20 @@ alone does not tell you whether you were affected.
6
6
  edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
7
7
  defect; those are called out below.
8
8
 
9
+ ## 0.6.61
10
+
11
+ - **Fixed** `api-errors.md` listing `name` among what a structured clone keeps. It keeps `message`,
12
+ `stack` and `cause`; `name` survives only for the seven built-in error types, and everything
13
+ else is normalised to `'Error'` — so every one of edfcore's seven classes arrives from a
14
+ `postMessage` named `Error`.
15
+ - It is the one clause on that page a reader acts on. The section is about what to do when
16
+ `edfErrorKind` is gone, and two paragraphs later the page says `error.name` is the concrete
17
+ class's name, "`'EdfFormatError'` rather than `'Error'`". The obvious fallback in a worker is
18
+ therefore to branch on `name`, and on the receiving side that branch never matches.
19
+ - The advice the section ends with is unchanged and was always right: send the discriminator
20
+ yourself. The test clones all six constructible classes through `structuredClone`, which is the
21
+ same algorithm `postMessage` uses, and checks a built-in keeps its name for contrast.
22
+
9
23
  ## 0.6.60
10
24
 
11
25
  - **Fixed** `header/signals.ts` saying that in `samplesPerRecord * bytesPerSample`, "Both numbers
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.60",
3
+ "version": "0.6.61",
4
4
  "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
5
5
  "keywords": [
6
6
  "edf",
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.6.60';
96
+ export const VERSION = '0.6.61';