edfcore 0.6.313 → 0.6.314
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.
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/docs/CHANGELOG.md +17 -0
- package/package.json +2 -2
- package/src/constants.ts +1 -1
package/dist/constants.d.ts
CHANGED
|
@@ -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.6.
|
|
112
|
+
export declare const VERSION = "0.6.314";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,23 @@ 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.6.314
|
|
10
|
+
|
|
11
|
+
- `vitest` 4.1.12 to **5.0.5**, a major, with the whole suite green on it: 630 files, 9,199 tests,
|
|
12
|
+
and both typecheck configs.
|
|
13
|
+
- Checked against this repository rather than taken on faith. Of 5.0's breaking changes, two could
|
|
14
|
+
have applied and neither did: `sequential` test and suite options were removed in favour of
|
|
15
|
+
`concurrent`, and nothing here used them — every `sequential` in `tests/` is prose or a local
|
|
16
|
+
variable; and `$` title variables in `test.each` no longer quote string values, which this suite
|
|
17
|
+
uses heavily (`'$name -> $annotation'`) but only ever for reporter output, never in an assertion.
|
|
18
|
+
- The Node floor is satisfied across the matrix. 5.0 requires `^22.12.0 || ^24.0.0 || >=26.0.0`,
|
|
19
|
+
`engines.node` here is `>=22.12.0`, and `ci.yml` runs 22.12, 24 and 26 — all three inside it.
|
|
20
|
+
- `npm audit` stays at zero.
|
|
21
|
+
- Noted and not acted on: the new reporter suggests `isolate: false` for about 3.7 s of the run.
|
|
22
|
+
Test isolation is not a performance knob to trade away in a suite that builds multi-megabyte
|
|
23
|
+
fixtures per file, and `config/vitest.config.ts` already explains why its one timing-related
|
|
24
|
+
setting is a hang detector rather than a budget.
|
|
25
|
+
|
|
9
26
|
## 0.6.313
|
|
10
27
|
|
|
11
28
|
- **Security.** `vitest` 4.1.11 to 4.1.12, and `npm audit` is back to zero.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edfcore",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.314",
|
|
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",
|
|
@@ -59,7 +59,7 @@
|
|
|
59
59
|
"@types/node": "^26.6.5",
|
|
60
60
|
"fast-check": "4.10.2",
|
|
61
61
|
"typescript": "6.0.3",
|
|
62
|
-
"vitest": "
|
|
62
|
+
"vitest": "5.0.5"
|
|
63
63
|
},
|
|
64
64
|
"scripts": {
|
|
65
65
|
"build": "tsc -p config/tsconfig.build.json",
|
package/src/constants.ts
CHANGED