edfcore 0.4.226 → 0.4.228

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

package/docs/CHANGELOG.md

@@ -6,6 +6,30 @@ 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.228
+
+- **Added** a test that actually runs `require()` of the built package from CommonJS. That it
+  works is the claim the Node floor rests on, stated five times — the README's compatibility
+  list, `installation.md`, `design-decisions.md`, the docblock in `src/index.ts`, and the comment
+  pinning 22.12 in the CI matrix — and nothing ran it. Nothing else in the suite could: the whole
+  repository is ESM under vitest, where a top-level `await` is ordinary and the condition that
+  breaks `require()` is invisible from inside. A child process now requires each of `dist/`'s
+  three entry points from a CommonJS realm, which makes Node itself the oracle — a graph with a
+  top-level `await` anywhere in it throws `ERR_REQUIRE_ASYNC_MODULE`, with no heuristic to agree
+  with the same mistake a reader of the source would. A negative control in the same run proves
+  the harness can fail.
+
+## 0.4.227
+
+- **Fixed** `npm run lint` not seeing any JavaScript in the repository. Biome's `files.includes`
+  listed `**/*.ts`, `**/*.json` and `**/*.jsonc`, and `includes` is a filter rather than an
+  addition — so `scripts/release.mjs`, `scripts/fetch-corpus.mjs`, `tests/support/browser-realm.mjs`
+  and `website/astro.config.mjs` were excluded outright, and asking Biome to check one by name
+  answered "these paths were provided but ignored". Three of the four were in a state lint would
+  have rejected: `fetch-corpus.mjs` had an unsorted import block, which is the `organizeImports`
+  error 0.4.225 was about. The release script has been edited in three of the last thirty releases
+  with no formatter or linter over it at all.
+
 ## 0.4.226
 
 - **Added** a recovery message for the one release step the 0.4.200 revert cannot reach. By the

package/package.json

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