edfcore 0.4.361 → 0.4.362

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.361";
112
+ export declare const VERSION = "0.4.362";
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.361';
82
+ export const VERSION = '0.4.362';
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.362
10
+
11
+ - **Added** a check over the edfcore column of the capabilities table on `comparison.md`. Seven
12
+ rows, and only one column this repository is entitled to check: the other four describe packages
13
+ nobody here controls, surveyed at a point in time, and asserting anything about them would be
14
+ asserting about someone else's release schedule. The claim under test is that every "Yes" in our
15
+ own column is true of the package as it stands.
16
+ - Worth checking because a comparison table is the most self-serving thing a project publishes and
17
+ the one a reader is least able to verify. The two rows the page itself calls load-bearing are the
18
+ two easiest to overstate, so both are demonstrated rather than asserted: random access by a
19
+ partial read counted through a recording source and landing past the middle of the file, and
20
+ EDF+D by a gap that puts record 3 at 13 seconds where the nominal grid would put it at 3.
21
+
9
22
  ## 0.4.361
10
23
 
11
24
  - **Added** a check over the error-class table on `api-errors.md`. Seven classes, each with an
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.361",
3
+ "version": "0.4.362",
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.361';
96
+ export const VERSION = '0.4.362';