edfcore 0.4.262 → 0.4.264

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

package/docs/CHANGELOG.md

@@ -6,6 +6,39 @@ 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.264
+
+- **Widened** the guard added in 0.4.239, which enforced the narrower half of its own rule. It
+  forbade a test globbing a TypeScript file out of `website/` and said nothing about importing
+  one, which reaches the same vite transform by the more obvious route — and the transform is what
+  resolves `website/tsconfig.json` and its `astro/tsconfigs/strict`, which the CI `check` job
+  never installs. Confirmed rather than assumed: `import { buildSampleEdf } from
+  '../../website/src/scripts/sample-edf.js'` passes locally and dies with the same
+  `[TSCONFIG_ERROR]` with `website/node_modules` moved aside, which is exactly how six versions
+  were lost in 0.4.237. Static imports, re-exports and `import()` are all covered now, and the
+  file is named for the boundary rather than for globs.
+- Comments are stripped before the scan, the rule 0.4.232 arrived at for the same reason: this
+  file's own docblock quotes the offending import to explain it, and the first run of the widened
+  check reported itself.
+
+## 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

package/package.json

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