@akiojin/unity-mcp-server 2.41.3 → 2.41.4

package/README.md

@@ -332,6 +332,30 @@ npm uninstall -g @akiojin/unity-mcp-server
 npm install -g @akiojin/unity-mcp-server
 ```
 
+### Native Module (better-sqlite3) Issues
+
+If you encounter errors related to `better-sqlite3` during installation or startup:
+
+**Symptom**: Installation fails with `node-gyp` errors, or startup shows "Could not locate the bindings file."
+
+**Cause**: The package includes prebuilt native binaries for supported platforms (Linux/macOS/Windows × x64/arm64 × Node 18/20/22). If your platform isn't supported or the prebuilt fails to load, the system falls back to WASM.
+
+**Solution 1 - Use WASM fallback (recommended for unsupported platforms)**:
+
+```bash
+# Skip native build and use sql.js WASM fallback
+UNITY_MCP_SKIP_NATIVE_BUILD=1 npm install @akiojin/unity-mcp-server
+```
+
+**Solution 2 - Force native rebuild**:
+
+```bash
+# Force rebuild from source (requires build tools)
+UNITY_MCP_FORCE_NATIVE=1 npm install @akiojin/unity-mcp-server
+```
+
+**Note**: WASM fallback is fully functional but may have slightly slower performance for large codebases. Code index features work normally in either mode.
+
 ### MCP Client Shows "Capabilities: none"
 
 If your MCP client (Claude Code, Cursor, etc.) shows "Capabilities: none" despite successful connection:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akiojin/unity-mcp-server",
-  "version": "2.41.3",
+  "version": "2.41.4",
   "description": "MCP server and Unity Editor bridge — enables AI assistants to control Unity for AI-assisted workflows",
   "type": "module",
   "main": "src/core/server.js",

package/src/core/sqliteFallback.js

@@ -1,18 +1,17 @@
 import fs from 'fs';
 import path from 'path';
-import { fileURLToPath } from 'url';
 import { createRequire } from 'module';
 import initSqlJs from 'sql.js';
 
 // Create a lightweight better-sqlite3 compatible surface using sql.js (WASM)
 export async function createSqliteFallback(dbPath) {
+  // Use Node's module resolution to find sql.js regardless of package manager (npm, pnpm, yarn)
+  // require.resolve('sql.js') returns the main entry point (dist/sql-wasm.js)
+  // so we just need sql-wasm.wasm in the same directory
   const require = createRequire(import.meta.url);
-  const moduleDir = path.dirname(fileURLToPath(import.meta.url));
-  const pkgRoot = path.resolve(moduleDir, '..', '..');
-  const wasmPath = require.resolve('sql.js/dist/sql-wasm.wasm', {
-    // Resolve from package-local node_modules first, then workspace root
-    paths: [path.join(pkgRoot, 'node_modules'), path.join(pkgRoot, '..', 'node_modules')]
-  });
+  const sqlJsPath = require.resolve('sql.js');
+  const sqlJsDir = path.dirname(sqlJsPath);
+  const wasmPath = path.resolve(sqlJsDir, 'sql-wasm.wasm');
   const SQL = await initSqlJs({ locateFile: () => wasmPath });
 
   const loadDb = () => {