edfcore 0.4.222 → 0.4.224

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.222";
112
+ export declare const VERSION = "0.4.224";
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.222';
82
+ export const VERSION = '0.4.224';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,22 @@ 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.224
10
+
11
+ - **Changed** the barrel type parser to live once, in `tests/support/barrel-types.ts`, instead of
12
+ twice. The second copy was written in 0.4.220 by reading the first, which is how it inherited a
13
+ blind spot that had been there since the first commit — and 0.4.222 and 0.4.223 then fixed the
14
+ same line in two files, three releases apart. Two copies of a rule are two chances to hold a
15
+ different one; the rule that a type is public because it leaves the barrel now has one home.
16
+
17
+ ## 0.4.223
18
+
19
+ - **Fixed** the same blind spot in the type parser added by 0.4.220. It read only
20
+ `export type { … } from` blocks, so `FileHandleLike` was outside the documentation check as well
21
+ as outside the count 0.4.222 corrected. Nothing was actually undocumented — that type is
22
+ described on `api-sources.md` — but it was exempt by accident rather than by the recorded list,
23
+ which is the state the list exists to prevent. Both parsers now read both shapes and see 65.
24
+
9
25
  ## 0.4.222
10
26
 
11
27
  - **Fixed** the README's public-type count, which said 64 and should say 65, and the guard that was
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.222",
3
+ "version": "0.4.224",
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.222';
96
+ export const VERSION = '0.4.224';