edfcore 0.4.197 → 0.4.199

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

package/dist/options.d.ts

@@ -2,9 +2,10 @@
  * Numeric options, refused rather than silently coerced.
  *
  * Layer 1. Imports one constant and nothing else, so every layer can reach it — which is the
- * point: `maxMaterializeBytes` is read in six modules spread across the stack — `io/read.ts`,
+ * point: `maxMaterializeBytes` is resolved in six modules spread across the stack — `io/read.ts`,
  * `decode/digital.ts`, `decode/physical.ts`, `record-index.ts`, `envelope.ts` and `validate.ts` —
- * and a guard that only one of them applies is not a guard.
+ * and read raw and handed on in two more, `io/cached.ts` and `biosemi.ts`. A guard that only one
+ * of the eight applies is not a guard.
  *
  * These options are typed `number`, which admits `NaN` and `Infinity`, and both arrive easily:
  * `Number(process.env.EDF_BUDGET)`, `Number(searchParams.get('block'))` and any absent key in a

package/dist/options.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"options.d.ts","sourceRoot":"","sources":["../src/options.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAIH;;;;GAIG;AACH,wBAAgB,mBAAmB,CACjC,KAAK,EAAE,MAAM,GAAG,SAAS,EACzB,IAAI,EAAE,MAAM,EACZ,QAAQ,EAAE,MAAM,GACf,MAAM,CAQR;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,wBAAwB,CAAC,KAAK,EAAE,MAAM,GAAG,SAAS,GAAG,MAAM,CAQ1E"}
+{"version":3,"file":"options.d.ts","sourceRoot":"","sources":["../src/options.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAIH;;;;GAIG;AACH,wBAAgB,mBAAmB,CACjC,KAAK,EAAE,MAAM,GAAG,SAAS,EACzB,IAAI,EAAE,MAAM,EACZ,QAAQ,EAAE,MAAM,GACf,MAAM,CAQR;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,wBAAgB,wBAAwB,CAAC,KAAK,EAAE,MAAM,GAAG,SAAS,GAAG,MAAM,CAQ1E"}

package/dist/options.js

@@ -2,9 +2,10 @@
  * Numeric options, refused rather than silently coerced.
  *
  * Layer 1. Imports one constant and nothing else, so every layer can reach it — which is the
- * point: `maxMaterializeBytes` is read in six modules spread across the stack — `io/read.ts`,
+ * point: `maxMaterializeBytes` is resolved in six modules spread across the stack — `io/read.ts`,
  * `decode/digital.ts`, `decode/physical.ts`, `record-index.ts`, `envelope.ts` and `validate.ts` —
- * and a guard that only one of them applies is not a guard.
+ * and read raw and handed on in two more, `io/cached.ts` and `biosemi.ts`. A guard that only one
+ * of the eight applies is not a guard.
  *
  * These options are typed `number`, which admits `NaN` and `Infinity`, and both arrive easily:
  * `Number(process.env.EDF_BUDGET)`, `Number(searchParams.get('block'))` and any absent key in a

package/dist/options.js.map

@@ -1 +1 @@
-{"version":3,"file":"options.js","sourceRoot":"","sources":["../src/options.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAEH,OAAO,EAAE,6BAA6B,EAAE,MAAM,gBAAgB,CAAC;AAE/D;;;;GAIG;AACH,MAAM,UAAU,mBAAmB,CACjC,KAAyB,EACzB,IAAY,EACZ,QAAgB;IAEhB,IAAI,KAAK,KAAK,SAAS;QAAE,OAAO,QAAQ,CAAC;IACzC,IAAI,MAAM,CAAC,QAAQ,CAAC,KAAK,CAAC;QAAE,OAAO,KAAK,CAAC;IACzC,MAAM,IAAI,UAAU,CAClB,WAAW,IAAI,qCAAqC,MAAM,CAAC,KAAK,CAAC,oBAAoB;QACnF,kFAAkF;QAClF,qCAAqC,CACxC,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,UAAU,wBAAwB,CAAC,KAAyB;IAChE,MAAM,MAAM,GAAG,mBAAmB,CAAC,KAAK,EAAE,qBAAqB,EAAE,6BAA6B,CAAC,CAAC;IAChG,IAAI,MAAM,IAAI,CAAC;QAAE,OAAO,MAAM,CAAC;IAC/B,MAAM,IAAI,UAAU,CAClB,6DAA6D,MAAM,0BAA0B;QAC3F,0DAA0D;QAC1D,GAAG,6BAA6B,gBAAgB,CACnD,CAAC;AACJ,CAAC"}
+{"version":3,"file":"options.js","sourceRoot":"","sources":["../src/options.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAEH,OAAO,EAAE,6BAA6B,EAAE,MAAM,gBAAgB,CAAC;AAE/D;;;;GAIG;AACH,MAAM,UAAU,mBAAmB,CACjC,KAAyB,EACzB,IAAY,EACZ,QAAgB;IAEhB,IAAI,KAAK,KAAK,SAAS;QAAE,OAAO,QAAQ,CAAC;IACzC,IAAI,MAAM,CAAC,QAAQ,CAAC,KAAK,CAAC;QAAE,OAAO,KAAK,CAAC;IACzC,MAAM,IAAI,UAAU,CAClB,WAAW,IAAI,qCAAqC,MAAM,CAAC,KAAK,CAAC,oBAAoB;QACnF,kFAAkF;QAClF,qCAAqC,CACxC,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,UAAU,wBAAwB,CAAC,KAAyB;IAChE,MAAM,MAAM,GAAG,mBAAmB,CAAC,KAAK,EAAE,qBAAqB,EAAE,6BAA6B,CAAC,CAAC;IAChG,IAAI,MAAM,IAAI,CAAC;QAAE,OAAO,MAAM,CAAC;IAC/B,MAAM,IAAI,UAAU,CAClB,6DAA6D,MAAM,0BAA0B;QAC3F,0DAA0D;QAC1D,GAAG,6BAA6B,gBAAgB,CACnD,CAAC;AACJ,CAAC"}

package/docs/CHANGELOG.md

@@ -6,6 +6,21 @@ 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.199
+
+- **Corrected** the title of `documented-examples.test-d.ts`, which read "The documented examples
+  in the docs compile". Three do. The three pages it covers carry 55 `ts` fences, and each covered
+  example needs a compiled twin written by hand, so the set is small on purpose — but a maintainer
+  reading the title would think a new snippet was already checked.
+
+## 0.4.198
+
+- **Corrected** the list of budget readers in `src/options.ts`. It named six modules; eight read
+  `maxMaterializeBytes`. `biosemi.ts` and `io/cached.ts` were missing, and neither is drift — both
+  already read it when 905810c, whose subject is "Name the six modules that read the budget", was
+  written. They read the raw option and hand it on rather than resolving it, so the six are now
+  named as the resolvers and the two as what they are.
+
 ## 0.4.197
 
 - **Corrected** the consumed-version count in `scripts/release.mjs`, which had drifted in the file

package/package.json

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

package/src/options.ts

@@ -2,9 +2,10 @@
  * Numeric options, refused rather than silently coerced.
  *
  * Layer 1. Imports one constant and nothing else, so every layer can reach it — which is the
- * point: `maxMaterializeBytes` is read in six modules spread across the stack — `io/read.ts`,
+ * point: `maxMaterializeBytes` is resolved in six modules spread across the stack — `io/read.ts`,
  * `decode/digital.ts`, `decode/physical.ts`, `record-index.ts`, `envelope.ts` and `validate.ts` —
- * and a guard that only one of them applies is not a guard.
+ * and read raw and handed on in two more, `io/cached.ts` and `biosemi.ts`. A guard that only one
+ * of the eight applies is not a guard.
  *
  * These options are typed `number`, which admits `NaN` and `Infinity`, and both arrive easily:
  * `Number(process.env.EDF_BUDGET)`, `Number(searchParams.get('block'))` and any absent key in a