edfcore 0.4.377 → 0.4.378

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.377";
112
+ export declare const VERSION = "0.4.378";
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.377';
82
+ export const VERSION = '0.4.378';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,23 @@ 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.378
10
+
11
+ - **Added** a check that the browser inspector uploads nothing, which is the most consequential
12
+ claim on the site. `demo.astro` says a browser can read these files "so a researcher never has to
13
+ hand a patient recording to a server", and somebody will drop a real clinical recording on that
14
+ page on the strength of that sentence.
15
+ - It is a claim about an absence, and nothing notices an absence breaking. A copy button that
16
+ reported usage, an error handler that posted a stack trace with a filename in it, an analytics
17
+ snippet in the shared layout — each is a normal thing to add to a website, and each would make
18
+ the sentence false without changing anything a visitor can see. So every source the site ships is
19
+ scanned for a way to send bytes: `fetch`, `XMLHttpRequest`, `sendBeacon`, `WebSocket`,
20
+ `EventSource`, a form, a remote dynamic import.
21
+ - `navigator.clipboard` is allowed by name rather than by permitting `navigator` generally, and the
22
+ pattern is asserted to still reject `navigator.sendBeacon` — the primitive built for exactly the
23
+ thing this forbids. The check covers the layout too, since the promise is about the page a
24
+ visitor is on and the layout wraps it.
25
+
9
26
  ## 0.4.377
10
27
 
11
28
  - **Added** a check that the exports badge and the API-surface table on the README show the same
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.377",
3
+ "version": "0.4.378",
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.377';
96
+ export const VERSION = '0.4.378';