edfcore 0.4.483 → 0.4.484
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 +13 -0
- package/package.json +1 -1
- 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.4.
|
|
112
|
+
export declare const VERSION = "0.4.484";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,19 @@ 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.484
|
|
10
|
+
|
|
11
|
+
- **Moved** the 31 MB fixture builds in `read-pattern.test.ts` into a `beforeAll` with a budget of
|
|
12
|
+
its own. All three builders already memoised, so only the first caller paid — but "the first
|
|
13
|
+
caller" is a test body with vitest's five-second default, and building 31 MB of records inside
|
|
14
|
+
it is most of that on an idle machine and more than it on a loaded one.
|
|
15
|
+
- The two tests that happen to ask first, one per fixture, then fail on a timeout that has nothing
|
|
16
|
+
to do with what they assert. Both were seen failing under coverage instrumentation while the
|
|
17
|
+
same run passed without it, which is the shape of failure that gets rerun rather than read.
|
|
18
|
+
- This is what 0.4.417 and 0.4.418 did for `spec-references.test.ts`, in that order and for the
|
|
19
|
+
same reason: memoising alone moves the cost onto whichever test runs first, and a `beforeAll` is
|
|
20
|
+
where a cost belonging to the file rather than to one case is supposed to sit.
|
|
21
|
+
|
|
9
22
|
## 0.4.483
|
|
10
23
|
|
|
11
24
|
- **Added** the whitespace-at-the-ends cases for the prefiltering conformance check, and a comment
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED