edfcore 0.4.265 → 0.4.266

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
109
109
  readonly reserved: 224;
110
110
  };
111
111
  /** Published package version. Kept in sync with package.json by a test. */
112
- export declare const VERSION = "0.4.265";
112
+ export declare const VERSION = "0.4.266";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.4.265';
82
+ export const VERSION = '0.4.266';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,20 @@ alone does not tell you whether you were affected.
6
6
  edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
7
7
  defect; those are called out below.
8
8
 
9
+ ## 0.4.266
10
+
11
+ - **Added** a check that every `npx edfcore …` written in the documentation is one the CLI
12
+ accepts. The commands were checked two ways already and neither covered it: `api-surface.md`'s
13
+ count is compared with `--help`, and `cli-command-list.test.ts` asserts `--help` offers exactly
14
+ what the dispatch switch handles. Both compare the CLI with itself. The sixteen invocations
15
+ spread across the README, the CLI page and the guides — the lines a reader actually copies into
16
+ a terminal — were checked by nobody, and renaming a command is exactly the change that would
17
+ leave both existing checks green while every page still named the old one.
18
+ - Driven through `runCli` rather than `parseArgs`, because an unknown command is not a parse
19
+ error: `parseArgs` puts any non-flag word in the command slot quite happily, so checking the
20
+ parser would have passed on `edfcore summary`. Exit code 2 is the documented contract for bad
21
+ usage, and that is what this asserts against.
22
+
9
23
  ## 0.4.265
10
24
 
11
25
  - **Added** the unit test `printable` never had. It is the smallest module in the package and its
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.265",
3
+ "version": "0.4.266",
4
4
  "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
5
5
  "keywords": [
6
6
  "edf",
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.4.265';
96
+ export const VERSION = '0.4.266';