edfcore 0.4.1 → 0.4.2

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.1";
+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.1';
+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/docs/CHANGELOG.md

@@ -6,6 +6,12 @@ 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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.1",
+  "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",

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.1';
+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