edfcore 0.4.398 → 0.4.400

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

package/docs/CHANGELOG.md

@@ -6,6 +6,34 @@ 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.400
+
+- **Added** a check that the two tsconfigs differ only where they are meant to. `npm run typecheck`
+  runs both on purpose — the build config compiles `src/` with `lib: ["ES2022"]` and `types: []` so
+  the DOM and `@types/node` cannot leak into the published declarations — and AGENTS.md states that
+  split. What it does not state is that everything else about them has to match.
+- That is the half with consequences. Every strictness flag in the root config is the setting the
+  suite is written under, including the `tests/types/*.test-d.ts` files whose job is to prove the
+  public API compiles for a consumer. Turn `noUncheckedIndexedAccess` off there alone and they keep
+  passing while they stop testing what they claim: `src/` still compiles strictly, and the snippet
+  asserting a consumer's experience is now checked under settings no consumer has.
+- The repository has already paid for that flag once. Until 0.4.259 the snippet AGENTS.md tells
+  agents to copy ended `chunks[0].signals[0].digital` and did not compile in a strict project.
+- The eleven strictness flags are also asserted individually, so turning one off in *both* configs —
+  which a comparison alone would call agreement — still fails. Divergences must be named, and a
+  named divergence the configs have since settled fails too, because a stale exception is a hole.
+
+## 0.4.399
+
+- **Added** to `verify:tarball` the three files npm packs by convention rather than because `files`
+  asks for it: `package.json`, `README.md` and `LICENSE`. `files` is an allow-list and none of the
+  three is on it, so all three ship on a rule this repository does not state and cannot see.
+- A package that arrives without `LICENSE` is an MIT package whose terms are not in it, which is
+  the half of 0.4.398 a text comparison cannot reach. Without `README.md` the npm page is blank —
+  the first thing anyone sees of the project, and the last thing anyone would think to check.
+- `.npmignore` is what makes this reachable rather than theoretical: it overrides `files` outright,
+  so adding one for an unrelated reason can take all three out at once.
+
 ## 0.4.398
 
 - **Added** a check that the licence is one licence. `package.json` declares `"license": "MIT"` —

package/package.json

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