edfcore 0.6.62 → 0.6.63

package/README.md

@@ -129,6 +129,11 @@ for it. JavaScript didn't. This is every EDF package on npm, surveyed in mid-202
 | Errors | `console.warn` and `null`, or bare thrown strings; nothing typed or located |
 | Header validation | Essentially none. No size checks, no degenerate-range checks |
 
+Those rows describe the packages as published to npm. `@epicurrents/edf-reader`'s repository
+does random access and BDF, and its published artifact predates a good deal of that work — the
+[comparison page](https://edfcore.vercel.app/docs/comparison) has the column-by-column version
+and says which claims that survey verified and which it did not.
+
 So people building EEG viewers don't reach for an EDF package. They hand-roll a parser and
 reproduce the same bugs.
 

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

package/docs/CHANGELOG.md

@@ -6,6 +6,22 @@ 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.6.63
+
+- **Fixed** the README contradicting itself about another package inside one screen. The "Before
+  edfcore" table says "Nothing published does byte-range reads" and "No published package can
+  read" BDF; two paragraphs below it, the same README credits `@epicurrents/edf-reader` with
+  "real TAL parsing, real partial reads, BDF support".
+- The reconciliation was already written and lived only on `comparison.md`, which marks both as
+  Yes for that project and then says to read its column "as describing its repository, rather
+  than the artifact currently on npm", because the published artifact predates a good deal of the
+  work in the repository. The README's rows say "published" and mean exactly that; nothing on the
+  page said so.
+- One paragraph under the table now carries that distinction and links to the page that makes it.
+  No claim about anyone else's package changed: this repository is not entitled to make one, which
+  is why `comparison-column.test.ts` checks only the edfcore column. What the new test checks is
+  ours — that the README still carries the qualification its own next paragraph makes necessary.
+
 ## 0.6.62
 
 - **Fixed** `api-errors.md` publishing `EdfFormatErrorInit` a field short. It was written

package/package.json

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