edfcore 0.4.376 → 0.4.377

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.376";
112
+ export declare const VERSION = "0.4.377";
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.376';
82
+ export const VERSION = '0.4.377';
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.377
10
+
11
+ - **Added** a check that the exports badge and the API-surface table on the README show the same
12
+ number, and a check on the reason they can. `/api.json` sums the runtime exports of the three
13
+ published entry points at build time; `api-surface.test.ts` counts the same thing from the
14
+ barrels and asserts the table. Two counters, one number, printed a screen apart on the same page.
15
+ - They agree because the three entry points share no runtime name, so a sum is the same as a union
16
+ — and nothing stated that. Re-exporting `openEdf` from `edfcore/node` so a Node consumer needs
17
+ one import is an obvious convenience, and it would make the badge count it twice: 79 above a
18
+ table reading 78, on the page a reader is looking at to decide whether to install the package.
19
+ Neither number would be wrong about what it measures, which is what makes the disagreement hard
20
+ to explain and easy to ship.
21
+
9
22
  ## 0.4.376
10
23
 
11
24
  - **Fixed** a gap in `.gitignore`: `.venv/` was not in it. `scripts/golden/README.md` tells you to
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.376",
3
+ "version": "0.4.377",
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.376';
96
+ export const VERSION = '0.4.377';