edfcore 0.4.227 → 0.4.228

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
109
109
  readonly reserved: 224;
110
110
  };
111
111
  /** Published package version. Kept in sync with package.json by a test. */
112
- export declare const VERSION = "0.4.227";
112
+ export declare const VERSION = "0.4.228";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.4.227';
82
+ export const VERSION = '0.4.228';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,19 @@ alone does not tell you whether you were affected.
6
6
  edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
7
7
  defect; those are called out below.
8
8
 
9
+ ## 0.4.228
10
+
11
+ - **Added** a test that actually runs `require()` of the built package from CommonJS. That it
12
+ works is the claim the Node floor rests on, stated five times — the README's compatibility
13
+ list, `installation.md`, `design-decisions.md`, the docblock in `src/index.ts`, and the comment
14
+ pinning 22.12 in the CI matrix — and nothing ran it. Nothing else in the suite could: the whole
15
+ repository is ESM under vitest, where a top-level `await` is ordinary and the condition that
16
+ breaks `require()` is invisible from inside. A child process now requires each of `dist/`'s
17
+ three entry points from a CommonJS realm, which makes Node itself the oracle — a graph with a
18
+ top-level `await` anywhere in it throws `ERR_REQUIRE_ASYNC_MODULE`, with no heuristic to agree
19
+ with the same mistake a reader of the source would. A negative control in the same run proves
20
+ the harness can fail.
21
+
9
22
  ## 0.4.227
10
23
 
11
24
  - **Fixed** `npm run lint` not seeing any JavaScript in the repository. Biome's `files.includes`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.227",
3
+ "version": "0.4.228",
4
4
  "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
5
5
  "keywords": [
6
6
  "edf",
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.4.227';
96
+ export const VERSION = '0.4.228';