edfcore 0.4.378 → 0.4.379

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.378";
112
+ export declare const VERSION = "0.4.379";
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.378';
82
+ export const VERSION = '0.4.379';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,19 @@ 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.379
10
+
11
+ - **Added** an execution of the "Oddities that bite implementers" section of `edf-format.md`, which
12
+ is that page's payload: seven paragraphs each naming a thing about EDF that produces a wrong
13
+ answer rather than an error. The page is written for someone about to write their own parser —
14
+ which the comparison page says is what people overwhelmingly do — so these are the claims most
15
+ likely to be acted on by a reader who never installs the package.
16
+ - Each is checked against the library, because that is the only way to check them and because each
17
+ is a place edfcore could regress into the naive behaviour being warned about. A date eighty years
18
+ wrong, a record count silently short, a rate of `Infinity`, a first header byte mangled by the
19
+ decoder that read it, and a redundant header size believed over the computed one — every
20
+ paragraph describes a bug that looks like working software.
21
+
9
22
  ## 0.4.378
10
23
 
11
24
  - **Added** a check that the browser inspector uploads nothing, which is the most consequential
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.378",
3
+ "version": "0.4.379",
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.378';
96
+ export const VERSION = '0.4.379';