edfcore 0.4.259 → 0.4.260

package/README.md

@@ -41,6 +41,8 @@ const [chunk] = await readWindow(recording, {
   startSeconds: 30,
   durationSeconds: 10,
 });
+// One chunk per contiguous run; a window that selects nothing returns none.
+if (chunk?.signals[0] === undefined) throw new Error('no data in that window');
 
 const microvolts = toPhysical(fp1, chunk.signals[0].digital);   // Float64Array
 ```

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

package/docs/CHANGELOG.md

@@ -6,6 +6,23 @@ 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.260
+
+- **Fixed** the README's quick start, which did not compile. It is the first code most people run
+  and it sits on the npm front page, and it ended `chunk.signals[0].digital` after destructuring
+  `const [chunk] = await readWindow(...)`. Under `noUncheckedIndexedAccess` — on in this repo and
+  in every strict TypeScript project — `chunk` is `EdfChunk | undefined` and so is `signals[0]`,
+  so the last line was `TS18048` and `TS2532`. One guard fixes both, and it is the guard the
+  reader needs anyway: a window that selects nothing returns no chunks, which is an ordinary
+  answer rather than an error.
+- **Added** it to `documented-examples.test-d.ts`, which has compiled three website snippets since
+  0.3.46 and never the README's. That comparison runs one way — every line a page has must exist
+  in the compiled copy — which catches a page gaining a line nothing compiles but not a page
+  losing one, since the copy keeps its own guard either way. So the quick start also gets a direct
+  check that the narrowing is still there, and the widening that lets the two texts be compared at
+  all: runs of spaces collapse, because a page aligns a trailing `// Float64Array` by eye and
+  Biome puts exactly one space before it.
+
 ## 0.4.259
 
 - **Fixed** the snippet in `AGENTS.md` that does not compile. Its "Using edfcore in generated

package/package.json

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