daftari 1.12.0 → 1.12.2
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/CHANGELOG.md +35 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,41 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [1.12.2] - 2026-05-26
|
|
11
|
+
|
|
12
|
+
### Fixed
|
|
13
|
+
|
|
14
|
+
- **MCPB now bundles `sqlite-vec-windows-x64`.** The v1.12.1 `.mcpb`
|
|
15
|
+
shipped fine on macOS but failed on Windows during scaffold /
|
|
16
|
+
reindex with `Cannot find package 'sqlite-vec-windows-x64'`. Same
|
|
17
|
+
root cause as the v1.10.0 sharp / better-sqlite3 problem: `sqlite-vec`
|
|
18
|
+
publishes per-platform binaries as `optionalDependencies`, so a
|
|
19
|
+
darwin-arm64 pack host only installs `sqlite-vec-darwin-arm64`.
|
|
20
|
+
`scripts/pack-mcpb.mjs` now also fetches the
|
|
21
|
+
`sqlite-vec-windows-x64@0.1.9` tarball and extracts `vec0.dll` into
|
|
22
|
+
`node_modules/sqlite-vec-windows-x64/`. No loader patch needed —
|
|
23
|
+
sqlite-vec's own loader resolves the right subpackage via
|
|
24
|
+
`import.meta.resolve()` based on `process.platform` /
|
|
25
|
+
`process.arch`. SQLite extensions are not NAPI / not ABI-bound, so
|
|
26
|
+
one binary per platform covers all Node versions.
|
|
27
|
+
|
|
28
|
+
## [1.12.1] - 2026-05-26
|
|
29
|
+
|
|
30
|
+
### Fixed
|
|
31
|
+
|
|
32
|
+
- **MCPB now runs on Node 24 hosts.** The v1.12.0 `.mcpb` only shipped
|
|
33
|
+
`better-sqlite3` binaries built against Node 22 (ABI v127); on a Node
|
|
34
|
+
24 host (ABI v137) the loader failed with `NODE_MODULE_VERSION`
|
|
35
|
+
mismatch and the server never booted. `scripts/pack-mcpb.mjs` now
|
|
36
|
+
fetches both ABIs for both platforms (4 binaries total: darwin-arm64
|
|
37
|
+
× {v127, v137} + win32-x64 × {v127, v137}) and stages each under
|
|
38
|
+
`build/Release-${platform}-${arch}-${modules}/`. The loader patch in
|
|
39
|
+
`better-sqlite3`'s `lib/database.js` now includes
|
|
40
|
+
`process.versions.modules` in the path, so the right binary is
|
|
41
|
+
selected at runtime for the host's Node version. Sharp and
|
|
42
|
+
onnxruntime-node are NAPI-based (ABI-stable across Node versions)
|
|
43
|
+
and don't need this treatment.
|
|
44
|
+
|
|
10
45
|
## [1.12.0] - 2026-05-26
|
|
11
46
|
|
|
12
47
|
### Added
|