edfcore 0.4.111 → 0.4.113

package/README.md

@@ -1,5 +1,8 @@
 # edfcore
 
+[![exports](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fedfcore.vercel.app%2Fapi.json&query=%24.exports.total&label=exports&color=blue)](https://edfcore.vercel.app/api.json)
+[![downloads](https://img.shields.io/npm/dt/edfcore?label=downloads)](https://www.npmjs.com/package/edfcore)
+
 edfcore reads EDF, EDF+, BDF and BDF+ biosignal files in TypeScript, in the browser and in
 Node. Real random access, no dependencies.
 
@@ -301,7 +304,10 @@ the reason to trust the reader.
 
 Every number above is asserted against the package by
 [`tests/integration/api-surface.test.ts`](tests/integration/api-surface.test.ts) — it counts the
-real exports, renders the real `--help`, and fails when this table drifts from either.
+real exports, renders the real `--help`, and fails when this table drifts from either. The
+`exports` badge at the top reads [`/api.json`](https://edfcore.vercel.app/api.json), which the
+documentation site generates at deploy time by importing the three published entry points and
+counting them, so it needs no maintenance at all.
 
 ---
 

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

package/docs/CHANGELOG.md

@@ -6,6 +6,20 @@ 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.113
+
+- **Removed** the npm version, types and licence badges added in 0.4.112. They restate what the
+  page already says a few lines down, and they pushed the one number worth showing into a row of
+  four. The badges are now the two counters: exports and downloads.
+
+## 0.4.112
+
+- **Added** shields.io badges to the README — npm version, exports, types and licence — and
+  `/api.json` on the documentation site to back the exports one.
+- The count is generated, not written. The site imports the three published entry points at deploy
+  time and counts them, so the badge follows the package without anyone editing a number. Three of
+  the four badges are served from npm's own metadata and update themselves the same way.
+
 ## 0.4.111
 
 - **Added** an "API surface" table to the README: three entry points, 78 functions, classes and

package/package.json

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