edfcore 0.4.353 → 0.4.355

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.4.353";
+export declare const VERSION = "0.4.355";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.353';
+export const VERSION = '0.4.355';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,35 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.4.355
+
+- **Fixed** a test of mine that could time out. The signature check added in 0.4.354 spawned `tsc`
+  inside an `it`, which takes a couple of seconds alone and rather more under a loaded suite —
+  past the default per-test timeout. It passed every run alone and failed the first time the whole
+  suite ran it.
+- Now compiled once at module scope, which is what `doc-snippets-compile.test.ts` next door
+  already does with its own compiler run. Collection time is not on a per-test clock, so the work
+  happens where it is not being timed, and nothing about the check weakens.
+
+## 0.4.354
+
+- **Added** a compile check over every signature the reference pages print. Four pages open each
+  function with a `ts` fence holding its declaration and nothing else — thirty-odd across
+  `api-primitives`, `api-reading`, `api-sources` and `api-validate` — and every one is hand-typed.
+  They are the first thing a reader sees for a function and what they write their call against.
+- `doc-snippets-compile.test.ts` compiles the fences that are complete programs and skips these: a
+  bare declaration imports nothing, so it never matched the filter that finds runnable examples.
+  The most load-bearing line on each reference page was the one nothing compiled.
+- Assignability is checked in BOTH directions, which is the difference between "the documented
+  shape is usable" and "the documented shape is the real one" — one direction alone accepts a page
+  that widens a parameter or narrows a return, and a widened parameter describes a function that
+  does not exist. Signatures are extracted per fence rather than by scanning the page, because a
+  lazy match for the parameter list's closing paren runs past it into the prose: `Promise<{ … }>`
+  has no `):` to stop at and the next parenthetical sentence does.
+- The types a declaration mentions are resolved through `barrel-types.ts` rather than a hard-coded
+  list. The first version used a list and missed four, which is the failure that helper was
+  extracted to stop repeating.
+
 ## 0.4.353
 
 - **Added** a cross-check between the two places `openEdf`'s cost is published. `large-files.md`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.353",
+  "version": "0.4.355",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.353';
+export const VERSION = '0.4.355';