edfcore 0.4.269 → 0.4.270

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.269";
112
+ export declare const VERSION = "0.4.270";
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.269';
82
+ export const VERSION = '0.4.270';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,21 @@ 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.270
10
+
11
+ - **Added** a check that every file this repository names in a comment is a file that is there.
12
+ Docblocks here point at each other constantly — `header/parse.ts` owns validation order,
13
+ `tal/ticks.ts` owns the tick conversion — and 324 of those references are written as backticked
14
+ paths that nothing reads. The `src/` half matters most: `removeComments: false` copies those
15
+ docblocks into `dist/*.d.ts`, so a path that stopped existing ships to every consumer as hover
16
+ text. Not hypothetical — `CHANGELOG.md` became `docs/CHANGELOG.md` at v0.4.1, and 0.4.264
17
+ renamed a test file when its rule outgrew its name.
18
+ - **Reworded** two comments that named things which were never files: a hypothetical
19
+ `guides/whatever.md` and the served route `api.json`, where the file is `api.json.ts`. Both
20
+ would have needed an exemption, and an exemption for "paths that are not paths" is how a check
21
+ stops meaning anything. `dist/` is the one that remains, because the build output is described
22
+ in several places and committed in none.
23
+
9
24
  ## 0.4.269
10
25
 
11
26
  - **Corrected** what `documented-examples.test-d.ts` claims to be. It opened by saying its five
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.269",
3
+ "version": "0.4.270",
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.269';
96
+ export const VERSION = '0.4.270';