edfcore 0.4.209 → 0.4.211

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.
@@ -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.209";
112
+ export declare const VERSION = "0.4.211";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.4.209';
82
+ export const VERSION = '0.4.211';
83
83
  //# sourceMappingURL=constants.js.map
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.4.211
10
+
11
+ - **Added** `is:inline` to the JSON-LD block in `Base.astro`, clearing the one hint `astro check`
12
+ has been printing. Without it the tag goes through Astro's script processing, which is for code
13
+ it is asked to bundle rather than for a literal payload that must reach the page exactly as
14
+ written — and this one is hand-escaped, so passing it through anything is the wrong default.
15
+ `astro check` now reports 0 errors, 0 warnings and 0 hints; the built `index.html` carries the
16
+ same graph it did before.
17
+
18
+ ## 0.4.210
19
+
20
+ - **Added** the guard for 0.4.208 and 0.4.209: `npm run lint` now passes `--error-on-warnings`, so
21
+ a warning fails the run instead of printing under it. Both diagnostics cleared in those releases
22
+ had been reported by every `npm run check` and every CI job without failing either, which is why
23
+ they lasted. This only became possible once the output was empty, and it is what stops it filling
24
+ up again.
25
+
9
26
  ## 0.4.209
10
27
 
11
28
  - **Changed** the `signals` row to a template literal, clearing the last standing lint diagnostic.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.209",
3
+ "version": "0.4.211",
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",
@@ -67,7 +67,7 @@
67
67
  "test": "vitest run --config config/vitest.config.ts",
68
68
  "test:watch": "vitest --config config/vitest.config.ts",
69
69
  "test:scratch": "vitest run --config config/vitest.scratch.config.ts",
70
- "lint": "biome check .",
70
+ "lint": "biome check --error-on-warnings .",
71
71
  "format": "biome format --write .",
72
72
  "check": "npm run lint && npm run typecheck && npm run build && npm run test",
73
73
  "corpus:fetch": "node scripts/fetch-corpus.mjs",
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.4.209';
96
+ export const VERSION = '0.4.211';