edfcore 0.4.337 → 0.4.338

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.337";
112
+ export declare const VERSION = "0.4.338";
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.337';
82
+ export const VERSION = '0.4.338';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,20 @@ 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.338
10
+
11
+ - **Added** a check that the three published copies of `ByteSource` agree. It is the one type a
12
+ caller implements rather than consumes — the extension point that lets a file, a blob, an object
13
+ store and an HTTP range share one path — so it is printed in full on `data-sources.md`, again on
14
+ `api-sources.md`, and declared in `src/types.ts`. Two of those are hand-typed copies of the
15
+ third.
16
+ - A drift here is worse than a stale sentence: someone writes an implementation against a printed
17
+ signature, TypeScript disagrees with the page, and the page is what they trusted. A dropped
18
+ `readonly`, a `close` that stopped being optional, a `ReadOptions` parameter that gained a
19
+ sibling — each is a one-word edit that neither `astro check` nor `tsc` can see, because a fenced
20
+ block is not code either of them compiles. `doc-snippets-compile.test.ts` compiles the fences
21
+ that are complete programs; this one is a declaration, so it is compared against the declaration.
22
+
9
23
  ## 0.4.337
10
24
 
11
25
  - **Added** an execution of the annotation listing on `quick-start.md`. The page's own format
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.337",
3
+ "version": "0.4.338",
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.337';
96
+ export const VERSION = '0.4.338';