yamlover 0.3.21 → 0.3.22

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "yamlover",
3
- "version": "0.3.21",
3
+ "version": "0.3.22",
4
4
  "description": "Browse a yamlover tree in the web: npx yamlover <root> serves a React SPA over a directory.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -34,8 +34,9 @@
34
34
  "test": "vitest run",
35
35
  "test:watch": "vitest"
36
36
  },
37
+ "comment:engines": "22.13, not 22: the engine's store imports the built-in node:sqlite, which is only available unflagged from Node 22.13 (bin/yamlover.js checks at startup and says so, since npm merely WARNS on an engines mismatch).",
37
38
  "engines": {
38
- "node": ">=22"
39
+ "node": ">=22.13"
39
40
  },
40
41
  "comment:deps": "No runtime dependencies: the client deps are bundled into dist/client by `vite build` and the server deps (ignore/js-yaml/xxhash-wasm, plus the thumbnail extractors jimp + ag-psd + @jsquash/webp + @jsquash/avif — dynamically imported so they stay out of the cold-start path) into dist/server.js by esbuild. The @jsquash codecs' .wasm is copied to dist/wasm by build.mjs (esbuild bundles only their JS glue). Everything below is build-/test-time only.",
41
42
  "devDependencies": {