edfcore 0.4.399 → 0.4.401
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 +36 -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.401";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,42 @@ 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.401
|
|
10
|
+
|
|
11
|
+
- **Added** a check that the palette has one definition. `tokens.css` opens by explaining the
|
|
12
|
+
pairing — the signal green carries the trace, the rose is semantic and marks events, and rose
|
|
13
|
+
rather than red because red-on-green is the one pairing red-green colourblindness collapses, with
|
|
14
|
+
the measured separation written down. That reasoning is worth something only while the colours it
|
|
15
|
+
describes are the colours a visitor sees.
|
|
16
|
+
- Three places cannot say `var(--signal)` and so restate the value. `og.svg`, because an SVG
|
|
17
|
+
exported by `qlmanage` has no stylesheet: nine literal hexes. The two `theme-color` metas, because
|
|
18
|
+
the browser paints the chrome before any CSS arrives — wrong values put a stale band above and
|
|
19
|
+
below a scrolling page, on phones, where nobody developing the site is looking. And
|
|
20
|
+
`TraceStrip.astro`, which reads the tokens at runtime and is right to, but whose fallbacks are the
|
|
21
|
+
palette written a third way in decimal RGB — the copy least likely to be recognised as one.
|
|
22
|
+
- Each is now required to be the specific token that does its job, resolved through `var()` the way
|
|
23
|
+
the cascade does: `theme-color` is `--bg` in each layer, the card's rose is on the annotation, and
|
|
24
|
+
each canvas fallback is its own token's default-theme value.
|
|
25
|
+
- The beam head is deliberately exempt. Its core is a near-white green brighter than any token,
|
|
26
|
+
because a phosphor blowout is additive light and there is no palette entry for it.
|
|
27
|
+
|
|
28
|
+
## 0.4.400
|
|
29
|
+
|
|
30
|
+
- **Added** a check that the two tsconfigs differ only where they are meant to. `npm run typecheck`
|
|
31
|
+
runs both on purpose — the build config compiles `src/` with `lib: ["ES2022"]` and `types: []` so
|
|
32
|
+
the DOM and `@types/node` cannot leak into the published declarations — and AGENTS.md states that
|
|
33
|
+
split. What it does not state is that everything else about them has to match.
|
|
34
|
+
- That is the half with consequences. Every strictness flag in the root config is the setting the
|
|
35
|
+
suite is written under, including the `tests/types/*.test-d.ts` files whose job is to prove the
|
|
36
|
+
public API compiles for a consumer. Turn `noUncheckedIndexedAccess` off there alone and they keep
|
|
37
|
+
passing while they stop testing what they claim: `src/` still compiles strictly, and the snippet
|
|
38
|
+
asserting a consumer's experience is now checked under settings no consumer has.
|
|
39
|
+
- The repository has already paid for that flag once. Until 0.4.259 the snippet AGENTS.md tells
|
|
40
|
+
agents to copy ended `chunks[0].signals[0].digital` and did not compile in a strict project.
|
|
41
|
+
- The eleven strictness flags are also asserted individually, so turning one off in *both* configs —
|
|
42
|
+
which a comparison alone would call agreement — still fails. Divergences must be named, and a
|
|
43
|
+
named divergence the configs have since settled fails too, because a stale exception is a hole.
|
|
44
|
+
|
|
9
45
|
## 0.4.399
|
|
10
46
|
|
|
11
47
|
- **Added** to `verify:tarball` the three files npm packs by convention rather than because `files`
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED