edfcore 0.4.261 → 0.4.263

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.261";
+export declare const VERSION = "0.4.263";
 //# 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.261';
+export const VERSION = '0.4.263';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,38 @@ 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.263
+
+- **Added** a sweep that compiles every self-contained example in the documentation, instead of
+  the five somebody remembered to write a twin for. `documented-examples.test-d.ts` keeps a
+  hand-written compiled copy per snippet, which is thorough and does not scale; the site has 102
+  fenced blocks that import from `edfcore`. All of them are now extracted, pointed at `src/`, and
+  compiled in one `tsc` under the flags this repository builds with. It costs about 1.5 seconds.
+- **Fixed** the example it found on `discontinuous.md`, which passed `chunk.signals[0]` to
+  `trimToWindow` — `EdfChunkSignal | undefined` under `noUncheckedIndexedAccess`, so
+  `TS2345`. That is the fourth page with this defect and the last one; 0.4.260 through 0.4.262
+  fixed the README, `reading-signals.md` and `annotations.md`.
+- Fences that cannot stand alone are skipped, on two markers that both mean "part of something
+  larger" rather than "wrong": `TS2304 Cannot find name`, for a block using a `recording` an
+  earlier block declared, and `TS1108`, for a block that is a function body shown without its
+  signature — which is how `api-errors.md` and `diagnostics.md` teach a handler. The number left
+  standing alone is asserted to stay above twenty, so the exemption cannot quietly grow to cover
+  everything.
+
+## 0.4.262
+
+- **Fixed** the worked example on `annotations.md` — read the sample under each sleep-stage event
+  — which was the other complete program that failed to compile on nothing but an unnarrowed
+  index. It ended `toPhysical(signal, chunk.signals[0].digital)`, and `chunk.signals[0]` is
+  `T | undefined` under `noUncheckedIndexedAccess` even though the call asked for exactly one
+  signal. It narrows with a `continue` now, which is the shape the loop around it already uses
+  twice, and the numbered comment says the thing worth knowing: asking for one signal does not
+  tell the compiler you got one.
+
+  That closes both of the complete-but-unsound examples the 102-fence sweep in 0.4.261 turned up.
+  The rest of the site's failures are fragments referencing a `recording` or a `header` declared
+  in an earlier block on the same page, which is what a reference page is for.
+
 ## 0.4.261
 
 - **Fixed** the opening example of `reading-signals.md`, which did not compile. It is the first

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.261",
+  "version": "0.4.263",
   "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.261';
+export const VERSION = '0.4.263';