edfcore 0.4.263 → 0.4.264
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 +15 -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.264";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
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.264
|
|
10
|
+
|
|
11
|
+
- **Widened** the guard added in 0.4.239, which enforced the narrower half of its own rule. It
|
|
12
|
+
forbade a test globbing a TypeScript file out of `website/` and said nothing about importing
|
|
13
|
+
one, which reaches the same vite transform by the more obvious route — and the transform is what
|
|
14
|
+
resolves `website/tsconfig.json` and its `astro/tsconfigs/strict`, which the CI `check` job
|
|
15
|
+
never installs. Confirmed rather than assumed: `import { buildSampleEdf } from
|
|
16
|
+
'../../website/src/scripts/sample-edf.js'` passes locally and dies with the same
|
|
17
|
+
`[TSCONFIG_ERROR]` with `website/node_modules` moved aside, which is exactly how six versions
|
|
18
|
+
were lost in 0.4.237. Static imports, re-exports and `import()` are all covered now, and the
|
|
19
|
+
file is named for the boundary rather than for globs.
|
|
20
|
+
- Comments are stripped before the scan, the rule 0.4.232 arrived at for the same reason: this
|
|
21
|
+
file's own docblock quotes the offending import to explain it, and the first run of the widened
|
|
22
|
+
check reported itself.
|
|
23
|
+
|
|
9
24
|
## 0.4.263
|
|
10
25
|
|
|
11
26
|
- **Added** a sweep that compiles every self-contained example in the documentation, instead of
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED