edfcore 0.4.0 → 0.4.2

package/README.md

@@ -352,7 +352,7 @@ whole point, since a reader that swapped the bounds would return plausible micro
 sign and invert the clinical reading of the trace.
 
 **Still open before 1.0.** Nothing named. The remaining work is API, not verification — see the
-0.3 note in [CHANGELOG.md](https://github.com/tayal-sarthak/edfcore/blob/main/CHANGELOG.md).
+0.3 note in [CHANGELOG.md](https://github.com/tayal-sarthak/edfcore/blob/main/docs/CHANGELOG.md).
 
 **Shipped since 0.1.6.** Min/max envelope decimation (`readEnvelope`,
 `readEnvelopeAtResolution`). BioSemi Status-byte helpers (`readTriggers`). Streaming iteration
@@ -361,7 +361,7 @@ the header and the validation report. Chunk joining that refuses to concatenate
 (`mergeChunks`). Timeline lookup with no read (`segmentAt`, `gapAt`, `contiguityOf`). Signal
 lookup by pattern (`matchSignals`) and ordered physical bounds (`physicalRangeOf`). See
 [API — helpers](https://edfcore.vercel.app/docs/api-helpers) and
-[CHANGELOG.md](https://github.com/tayal-sarthak/edfcore/blob/main/CHANGELOG.md).
+[CHANGELOG.md](https://github.com/tayal-sarthak/edfcore/blob/main/docs/CHANGELOG.md).
 
 **Still later, additive.** The `edffloat` logarithmic inverse transform, opt-in — still detected
 and rejected, because applying an inverse edfcore cannot verify against a real edffloat file is

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

package/dist/index.d.ts

@@ -8,7 +8,7 @@
  *
  * - NO import of a Node built-in, transitively. `edfcore/node` is the only module in this graph
  *   allowed one — the `bin` entry has its own, and nothing reaches it from here — and
- *   a packaging test greps the built universal bundle for the scheme prefix to prove it — which is
+ *   `public-api.test.ts` walks this module graph for the scheme prefix to prove it — which is
  *   also why that prefix is not written out anywhere in this file. It is what lets one build serve
  *   Node, browsers, Deno and Bun with no environment conditions in the exports map: conditions are
  *   the single largest source of ecosystem incompatibility, and a dual CJS/ESM build would load

package/dist/index.js

@@ -8,7 +8,7 @@
  *
  * - NO import of a Node built-in, transitively. `edfcore/node` is the only module in this graph
  *   allowed one — the `bin` entry has its own, and nothing reaches it from here — and
- *   a packaging test greps the built universal bundle for the scheme prefix to prove it — which is
+ *   `public-api.test.ts` walks this module graph for the scheme prefix to prove it — which is
  *   also why that prefix is not written out anywhere in this file. It is what lets one build serve
  *   Node, browsers, Deno and Bun with no environment conditions in the exports map: conditions are
  *   the single largest source of ecosystem incompatibility, and a dual CJS/ESM build would load

package/{CHANGELOG.md → docs/CHANGELOG.md}

@@ -6,6 +6,21 @@ 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.2
+
+- **Fixed** `src/index.ts` crediting "a packaging test" that "greps the built universal bundle" for
+  the `node:` prefix. The check is `public-api.test.ts`, and it walks the `src/` module graph — the
+  built bundle is what `browser-safety.test.ts` runs, for globals rather than imports.
+
+## 0.4.1
+
+- **Moved** `CHANGELOG.md` to `docs/CHANGELOG.md`. It still ships in the tarball, so the release
+  record is still readable out of `node_modules/edfcore/` — at the new path. That is the only
+  change in this release a consumer can observe.
+- The three build configs moved to `config/`, and every `npm` script now names its config instead
+  of relying on a tool's default lookup. Repository only: nothing under `src/` changed, so the API,
+  the shipped types and the arithmetic are identical to 0.4.0.
+
 ## 0.4.0
 
 The public API is unchanged: nothing was added, removed or renamed, and no arithmetic moved. This

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.0",
+  "version": "0.4.2",
   "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",
@@ -32,7 +32,7 @@
   "type": "module",
   "sideEffects": false,
   "files": [
-    "CHANGELOG.md",
+    "docs/CHANGELOG.md",
     "dist",
     "src"
   ],
@@ -62,11 +62,11 @@
     "vitest": "4.1.10"
   },
   "scripts": {
-    "build": "tsc -p tsconfig.build.json",
-    "typecheck": "tsc -p tsconfig.build.json --noEmit && tsc -p tsconfig.json",
-    "test": "vitest run",
-    "test:watch": "vitest",
-    "test:scratch": "vitest run --config vitest.scratch.config.ts",
+    "build": "tsc -p config/tsconfig.build.json",
+    "typecheck": "tsc -p config/tsconfig.build.json --noEmit && tsc -p tsconfig.json",
+    "test": "vitest run --config config/vitest.config.ts",
+    "test:watch": "vitest --config config/vitest.config.ts",
+    "test:scratch": "vitest run --config config/vitest.scratch.config.ts",
     "lint": "biome check .",
     "format": "biome format --write .",
     "check": "npm run lint && npm run typecheck && npm run build && npm run test",

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.0';
+export const VERSION = '0.4.2';

package/src/index.ts

@@ -8,7 +8,7 @@
  *
  * - NO import of a Node built-in, transitively. `edfcore/node` is the only module in this graph
  *   allowed one — the `bin` entry has its own, and nothing reaches it from here — and
- *   a packaging test greps the built universal bundle for the scheme prefix to prove it — which is
+ *   `public-api.test.ts` walks this module graph for the scheme prefix to prove it — which is
  *   also why that prefix is not written out anywhere in this file. It is what lets one build serve
  *   Node, browsers, Deno and Bun with no environment conditions in the exports map: conditions are
  *   the single largest source of ecosystem incompatibility, and a dual CJS/ESM build would load