@sbroenne/excelcli 2.1.0 → 2.1.2

package/README.md

@@ -14,9 +14,12 @@ npm install --global @sbroenne/excelcli
 excelcli --version
 ```
 
-Requires Node.js 18 or later, Windows x64 or Arm64 (x64 emulation), and
+Requires Node.js 18 or later, Windows x64 or ARM64, and
 Microsoft Excel 2016 or later. No separate .NET runtime is needed. Keep
 optional dependencies enabled so npm installs the matching Windows runtime.
+ARM64 Node.js selects the native ARM64 runtime; x64 Node.js selects x64,
+including on ARM64 Windows. A missing matching package is an error, not a
+fallback to another architecture.
 
 The launcher forwards arguments, standard input/output, and exit codes to the
 existing CLI. Excel operations and session management are unchanged.

package/lib/launcher.js

@@ -5,8 +5,6 @@ import { foregroundChild } from 'foreground-child';
 const require = createRequire(import.meta.url);
 
 export function createLauncher({ packageName, commandName }) {
-  const runtimePackageName = `${packageName}-win32-x64`;
-
   function resolveRuntime({
     platform = process.platform,
     arch = process.arch,
@@ -20,6 +18,7 @@ export function createLauncher({ packageName, commandName }) {
       throw new Error(`ExcelMcp requires Windows x64 or Arm64; this Node.js process is ${arch}.`);
     }
 
+    const runtimePackageName = `${packageName}-win32-${arch}`;
     try {
       return resolvePackage(runtimePackageName);
     } catch (cause) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sbroenne/excelcli",
-  "version": "2.1.0",
+  "version": "2.1.2",
   "description": "Excel automation CLI for Windows, distributed through npm.",
   "license": "MIT",
   "type": "module",
@@ -33,7 +33,8 @@
     "foreground-child": "^4.0.3"
   },
   "optionalDependencies": {
-    "@sbroenne/excelcli-win32-x64": "2.1.0"
+    "@sbroenne/excelcli-win32-x64": "2.1.2",
+    "@sbroenne/excelcli-win32-arm64": "2.1.2"
   },
   "publishConfig": {
     "access": "public",