edfcore 0.4.492 → 0.4.493

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.4.492";
112
+ export declare const VERSION = "0.4.493";
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.4.492';
82
+ export const VERSION = '0.4.493';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,22 @@ 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.4.493
10
+
11
+ - **Added** the two edges of `readHeader`'s prefetch decision, both of which could be moved with
12
+ the suite green.
13
+ - The upper one is the one that matters. Narrowing `<= 9999` refuses the hint for a file declaring
14
+ the most signals a header can — and the consequence is not a slower read but a wrong answer: the
15
+ second read is skipped, `parseHeader` gets a quarter of a kilobyte of a 2.56 MB header, and a
16
+ perfectly good recording is reported `SOURCE_TOO_SMALL`. At exactly one signal count.
17
+ - The other side of that guard is unreachable, and the test says so with a check rather than in
18
+ prose: the field is four ASCII bytes and `parseEdfInteger` admits no exponent, so `9999` is the
19
+ largest value that parses. Widening the field or admitting `9e9` makes the guard live, and fails
20
+ this in the same commit.
21
+ - The lower edge is a source that ends with the fixed header. `remaining` is zero, and asking for
22
+ zero bytes is still a read — a round trip over HTTP, and an entry in every read-count claim this
23
+ file makes.
24
+
9
25
  ## 0.4.492
10
26
 
11
27
  - **Added** a test that runs the worked example on `reading-signals.md`. That page carries the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.492",
3
+ "version": "0.4.493",
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.4.492';
96
+ export const VERSION = '0.4.493';