@sebastienrousseau/noyalib-wasm 0.0.17 → 0.0.18

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/README.md CHANGED
@@ -263,13 +263,21 @@ Browser + Node demos under
263
263
  |---|---|---|
264
264
  | [`node-stringify.js`](examples/node-stringify.js) | Node | `parse` + `stringify` round-trip. |
265
265
  | [`cst-edit.js`](examples/cst-edit.js) | Node | Lossless CST edit; comments + whitespace preserved. |
266
- | [`schema-validate.js`](examples/schema-validate.js) | Node | JSON Schema 2020-12 validation, good and bad cases. |
266
+ | [`paths-and-spans.js`](examples/paths-and-spans.js) | Node | `getPath`, `merge`, `getSource`, `spanAt`, `replaceSpan`, `setValue`, `commentsAt`. |
267
+ | [`json-compat.js`](examples/json-compat.js) | Node | `validateJson` — refuse YAML that JSON cannot represent (NaN / Infinity). |
267
268
  | [`browser/index.html`](examples/browser/index.html) | Browser | Live in-page YAML editor with a parsed-JSON pane. |
269
+ | [`benches/bench.js`](benches/bench.js) | Node | Throughput measured across the real JS↔wasm boundary. |
270
+
271
+ > The wasm build ships **no JSON Schema engine**. `validateJson` only
272
+ > checks JSON round-trip safety. For JSON Schema 2020-12 use
273
+ > `noyavalidate --schema`, or the `noyalib` crate's `validate-schema`
274
+ > feature.
268
275
 
269
276
  ```bash
270
277
  # Node:
271
278
  wasm-pack build --release --target nodejs crates/noyalib-wasm
272
279
  node crates/noyalib-wasm/examples/cst-edit.js
280
+ node crates/noyalib-wasm/examples/json-compat.js
273
281
 
274
282
  # Browser:
275
283
  wasm-pack build --release --target web crates/noyalib-wasm
@@ -294,9 +302,10 @@ python3 -m http.server # or any static-file server
294
302
 
295
303
  ## Compatibility
296
304
 
297
- **MSRV: Rust 1.85.0** stable. The `wasm-bindgen` 0.2 ecosystem
298
- floors the toolchain at 1.85; the core `noyalib` library
299
- itself stays at 1.75. CI verifies the floor on every PR via
305
+ **MSRV: Rust 1.86.0** stable a deliberate policy choice: one floor across the whole lockstep set,
306
+ with headroom for the dependency tree. No current dependency *requires*
307
+ 1.86 this crate still compiles on 1.85. The whole lockstep set,
308
+ including the core `noyalib` library, shares this floor. CI verifies the floor on every PR via
300
309
  the `Per-crate MSRV` workflow job. The bump policy lives in
301
310
  [`doc/POLICIES.md`](https://github.com/sebastienrousseau/noyalib/blob/main/doc/POLICIES.md#1-msrv-minimum-supported-rust-version).
302
311
 
Binary file
package/package.json CHANGED
@@ -5,7 +5,7 @@
5
5
  "Sebastien Rousseau <sebastian.rousseau@gmail.com>"
6
6
  ],
7
7
  "description": "WebAssembly (wasm-bindgen) bindings for the noyalib YAML library — browser-ready parse / serialise / lossless edit",
8
- "version": "0.0.17",
8
+ "version": "0.0.18",
9
9
  "license": "MIT OR Apache-2.0",
10
10
  "repository": {
11
11
  "type": "git",