edfcore 0.4.280 → 0.4.281

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.280";
112
+ export declare const VERSION = "0.4.281";
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.280';
82
+ export const VERSION = '0.4.281';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,20 @@ 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.281
10
+
11
+ - **Checked** that `sideEffects: false` is honest, rather than merely present. 0.4.230 read the
12
+ flag out of the manifest; this imports the three entry points in a fresh child realm and watches
13
+ what happens. A bundler reads that flag and feels free to drop any import whose bindings go
14
+ unused, so a module that did something at load — patched a global, started a timer, registered a
15
+ handler — would have licensed the bundler to delete behaviour a consumer depends on, with
16
+ nothing about the failure pointing back here.
17
+ - A child process because the question is about a fresh realm: by the time any test runs, the
18
+ parent has imported `src/` a hundred times over. Three things are watched — a new property on
19
+ `globalThis`, a timer, a `process` listener — which is not exhaustive and is what a load-time
20
+ side effect looks like in practice, each of them silent from the outside. Verified by adding one
21
+ of each to the barrel and watching both fail.
22
+
9
23
  ## 0.4.280
10
24
 
11
25
  - **Added** a check that the exit-code table on the CLI page is the code the CLI returns.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.280",
3
+ "version": "0.4.281",
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.280';
96
+ export const VERSION = '0.4.281';