yaver-cli 1.99.107 → 1.99.108

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/sdk-manifest.json +4 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "yaver-cli",
3
- "version": "1.99.107",
3
+ "version": "1.99.108",
4
4
  "mcpName": "io.github.kivanccakmak/yaver",
5
5
  "description": "Unified npm bootstrap for the Yaver agent, SDK injection, and local-first developer runtime",
6
6
  "bin": {
package/sdk-manifest.json CHANGED
@@ -39,11 +39,12 @@
39
39
  "hermesVersion": "0.81.5",
40
40
  "hermesBCVersion": 96,
41
41
  "supportedRNRange": "0.81.x",
42
- "compiledIn": true,
43
- "status": "pilot",
42
+ "compiledIn": false,
43
+ "status": "planned",
44
44
  "manifestResource": "runtime-families/family-b/sdk-manifest.json",
45
45
  "packageRoot": "mobile-family-b",
46
- "preferredPackageNames": ["sfmg"]
46
+ "preferredPackageNames": ["sfmg"],
47
+ "compiledInDisabledReason": "family-b declared compiledIn=true but the iOS binary only ships React 19.1.0 (mobile/package.json). The packageRoot directory mobile-family-b/ does not exist, so React 19.2.5 is NOT compiled into Yaver. The agent honored the preferredPackageNames hint and built SFMG against this family's contract (React 19.2.5), and Hermes crashed at JSObject::hasComputed with a corrupted HermesValue when SFMG's JSI calls hit the React 19.1.0 ABI on the device. Forcing this to false makes the runtime-family selector fall back to family-a (the real, compiled-in family) until a true family-b binary is built. To re-enable: actually compile React 19.2.5 + matching native modules into a separate iOS bundle slot, then flip this back to true."
47
48
  }
48
49
  ],
49
50
  "nativeModules": {