edfcore 0.4.347 → 0.4.348

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.347";
112
+ export declare const VERSION = "0.4.348";
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.347';
82
+ export const VERSION = '0.4.348';
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.4.348
10
+
11
+ - **Added** a check for what `index.locate` costs, against the two read counts `discontinuous.md`
12
+ prints — three for the first call, zero for a second one nearby.
13
+ - The zero is the one worth holding. A UI that calls `locate` on every pointer move is either free
14
+ or a request per frame, and nothing at the call site says which; a memo dropped in a refactor
15
+ changes no result at all, so no other test would notice. The three is worth holding for its
16
+ parenthesis rather than its size: records 0 and 5 are already known because `openEdf` probed
17
+ them, so the search starts from what the open already paid for.
18
+ - Also pinned: that the search reads one record at a time rather than widening to a range, which
19
+ would still answer correctly and cost far more over HTTP; and the file the page draws, whose span
20
+ of 16 and coverage of 6 are computed independently and differ by the ten seconds no record
21
+ covers.
22
+
9
23
  ## 0.4.347
10
24
 
11
25
  - **Added** an execution of the `bigint` ticks decision on `design-decisions.md`. It is defended
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.347",
3
+ "version": "0.4.348",
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.347';
96
+ export const VERSION = '0.4.348';