edfcore 0.4.447 → 0.4.449

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

package/docs/CHANGELOG.md

@@ -6,6 +6,42 @@ 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.449
+
+- **Added** a check that the sourcemaps in the published package point at files the package ships.
+  `sourceMap` and `declarationMap` in the build config and `src` in `files` are one feature: tsc
+  emits maps whose sources are `../src/x.ts` relative to `dist/` and inlines no `sourcesContent`,
+  so the maps resolve only because the TypeScript ships beside them. That is why
+  `check-tarball.mjs` refuses a tarball without `src/` with the words "the sourcemaps resolve to
+  nothing".
+- Nothing checked that the maps say what the arrangement assumes, and three edits break it while
+  failing nothing: dropping `src` from `files` to make the tarball smaller — 250 KB of TypeScript
+  for a package whose `dist` is what runs looks like dead weight; turning `sourcesContent` on,
+  which makes `src/` redundant right up until someone turns it off again; or turning either map off.
+- What breaks is not a build. It is a consumer stepping into `openEdf` in a debugger and landing in
+  compiled output, or "go to definition" on `EdfHeader` opening a `.d.ts` instead of the file whose
+  comments explain the field. The package still installs, still imports, still passes everything
+  here — what stops working is the reason `removeComments: false` and `declarationMap` are set at
+  all, that the source is what a reader reaches.
+
+## 0.4.448
+
+- **Added** tests for what `edfcore json` puts in a file you are about to pipe somewhere. Piping is
+  the whole reason the command exists — into `jq`, a manifest, a ticket, a spreadsheet a directory
+  sweep produced — which is why identification is opt-in here as it is in `formatHeader`.
+- `json` defends differently from the other two commands. `header` and `validate` redact, putting
+  a placeholder where a value was; `json` omits the key entirely, because an object recording that
+  a patient field existed and was withheld is a different thing for a machine to read.
+- The diagnostics are the quieter half. They are reduced to `code` and `severity` — no message, no
+  raw, no actual — so identification cannot arrive through a diagnostic that quoted the field it
+  was complaining about, and every identification diagnostic does quote it. That is achieved by an
+  object literal naming two properties, which is one careless spread away from carrying all of
+  them.
+- `trimEdfField` rather than `.trim()` is the third. `.trim()` leaves U+0000 in place, so on the
+  NUL-padded fields a large share of real writers emit, `JSON.stringify` escapes each one into a
+  six-character sequence inside the value — unreadable, and a disclosure of the field's exact
+  width.
+
 ## 0.4.447
 
 - **Added** a check that a machine which has not downloaded the corpus still gets a green suite.

package/package.json

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