edfcore 0.4.377 → 0.4.379

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

package/docs/CHANGELOG.md

@@ -6,6 +6,36 @@ 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.379
+
+- **Added** an execution of the "Oddities that bite implementers" section of `edf-format.md`, which
+  is that page's payload: seven paragraphs each naming a thing about EDF that produces a wrong
+  answer rather than an error. The page is written for someone about to write their own parser —
+  which the comparison page says is what people overwhelmingly do — so these are the claims most
+  likely to be acted on by a reader who never installs the package.
+- Each is checked against the library, because that is the only way to check them and because each
+  is a place edfcore could regress into the naive behaviour being warned about. A date eighty years
+  wrong, a record count silently short, a rate of `Infinity`, a first header byte mangled by the
+  decoder that read it, and a redundant header size believed over the computed one — every
+  paragraph describes a bug that looks like working software.
+
+## 0.4.378
+
+- **Added** a check that the browser inspector uploads nothing, which is the most consequential
+  claim on the site. `demo.astro` says a browser can read these files "so a researcher never has to
+  hand a patient recording to a server", and somebody will drop a real clinical recording on that
+  page on the strength of that sentence.
+- It is a claim about an absence, and nothing notices an absence breaking. A copy button that
+  reported usage, an error handler that posted a stack trace with a filename in it, an analytics
+  snippet in the shared layout — each is a normal thing to add to a website, and each would make
+  the sentence false without changing anything a visitor can see. So every source the site ships is
+  scanned for a way to send bytes: `fetch`, `XMLHttpRequest`, `sendBeacon`, `WebSocket`,
+  `EventSource`, a form, a remote dynamic import.
+- `navigator.clipboard` is allowed by name rather than by permitting `navigator` generally, and the
+  pattern is asserted to still reject `navigator.sendBeacon` — the primitive built for exactly the
+  thing this forbids. The check covers the layout too, since the promise is about the page a
+  visitor is on and the layout wraps it.
+
 ## 0.4.377
 
 - **Added** a check that the exports badge and the API-surface table on the README show the same

package/package.json

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