edfcore 0.4.376 → 0.4.378
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 +30 -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.378";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,36 @@ 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.378
|
|
10
|
+
|
|
11
|
+
- **Added** a check that the browser inspector uploads nothing, which is the most consequential
|
|
12
|
+
claim on the site. `demo.astro` says a browser can read these files "so a researcher never has to
|
|
13
|
+
hand a patient recording to a server", and somebody will drop a real clinical recording on that
|
|
14
|
+
page on the strength of that sentence.
|
|
15
|
+
- It is a claim about an absence, and nothing notices an absence breaking. A copy button that
|
|
16
|
+
reported usage, an error handler that posted a stack trace with a filename in it, an analytics
|
|
17
|
+
snippet in the shared layout — each is a normal thing to add to a website, and each would make
|
|
18
|
+
the sentence false without changing anything a visitor can see. So every source the site ships is
|
|
19
|
+
scanned for a way to send bytes: `fetch`, `XMLHttpRequest`, `sendBeacon`, `WebSocket`,
|
|
20
|
+
`EventSource`, a form, a remote dynamic import.
|
|
21
|
+
- `navigator.clipboard` is allowed by name rather than by permitting `navigator` generally, and the
|
|
22
|
+
pattern is asserted to still reject `navigator.sendBeacon` — the primitive built for exactly the
|
|
23
|
+
thing this forbids. The check covers the layout too, since the promise is about the page a
|
|
24
|
+
visitor is on and the layout wraps it.
|
|
25
|
+
|
|
26
|
+
## 0.4.377
|
|
27
|
+
|
|
28
|
+
- **Added** a check that the exports badge and the API-surface table on the README show the same
|
|
29
|
+
number, and a check on the reason they can. `/api.json` sums the runtime exports of the three
|
|
30
|
+
published entry points at build time; `api-surface.test.ts` counts the same thing from the
|
|
31
|
+
barrels and asserts the table. Two counters, one number, printed a screen apart on the same page.
|
|
32
|
+
- They agree because the three entry points share no runtime name, so a sum is the same as a union
|
|
33
|
+
— and nothing stated that. Re-exporting `openEdf` from `edfcore/node` so a Node consumer needs
|
|
34
|
+
one import is an obvious convenience, and it would make the badge count it twice: 79 above a
|
|
35
|
+
table reading 78, on the page a reader is looking at to decide whether to install the package.
|
|
36
|
+
Neither number would be wrong about what it measures, which is what makes the disagreement hard
|
|
37
|
+
to explain and easy to ship.
|
|
38
|
+
|
|
9
39
|
## 0.4.376
|
|
10
40
|
|
|
11
41
|
- **Fixed** a gap in `.gitignore`: `.venv/` was not in it. `scripts/golden/README.md` tells you to
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED