edfcore 0.6.63 → 0.6.64

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.63";
112
+ export declare const VERSION = "0.6.64";
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.63';
82
+ export const VERSION = '0.6.64';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,21 @@ 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.64
10
+
11
+ - **Fixed** `installation.md` counting `TextDecoder` among "the four platform features edfcore
12
+ relies on". It does not rely on it. `tal/grammar.ts` takes an ASCII fast path first, which is
13
+ what almost every recording's annotation text is, so the decoder is never built for them; and
14
+ when one is needed and absent the text run falls back to ISO-8859-1 with an
15
+ `ANNOTATION_TEXT_NOT_UTF8` diagnostic rather than throwing. The `null` branch in `utf8Decoder()`
16
+ exists for exactly that and its docblock says so.
17
+ - The sentence told a reader on a runtime without `TextDecoder` that they were unsupported, when
18
+ the library is built to carry on without one.
19
+ - No floor moved and nothing is asserted here about browser release history —
20
+ `browser-floor.test.ts` says why that is not a claim this repository can settle, and still pins
21
+ the four-item basis string. The new test deletes the global and reads a file each way, through
22
+ a fresh module registry, because `utf8Decoder()` memoises its answer — the `null` included.
23
+
9
24
  ## 0.6.63
10
25
 
11
26
  - **Fixed** the README contradicting itself about another package inside one screen. The "Before
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.63",
3
+ "version": "0.6.64",
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.63';
96
+ export const VERSION = '0.6.64';