Axe Linter VS Code Extension Fails to Start on M4 Mac (spawn error -86)

### Product

axe Linter

### Product Version

4.10.5

### Latest Version

- [x] I have tested the issue with the latest version of the product

### Issue Description

Hi Deque Support Team,

I’m encountering an issue with the axe Accessibility Linter extension for Visual Studio Code on a new Apple M4 MacBook.

When I enable the extension in VS Code, it fails to start and shows the following error:

`pgsql
Copy
Edit
[Error - 19:01:21] Starting client failed
Error: spawn Unknown system error -86
at ChildProcess.spawn (node:internal/child_process:420:11)
at Object.spawn (node:child_process:796:9)
at /Users//.vscode/extensions/deque-systems.vscode-axe-linter-4.10.5/dist/src/extension.js:2:264354`

After some investigation, this appears to be caused by the extension trying to spawn a binary compiled for x86_64, which fails on the ARM64 architecture of Apple Silicon — especially on the M4 chip.

System Details:

- macOS: Sonoma 14.x
- Mac chip: Apple M4
- VS Code version: [1.100.0]

Axe Linter extension version: 4.10.5

This error seems to suggest that the extension (or a subprocess within it) is not yet compatible with native ARM environments, or is missing a fallback for universal binaries.

Could you please confirm:

- Whether ARM64-native support is planned?
- If there's a temporary workaround other than switching to Rosetta + Intel VS Code?
- If a CLI-based alternative is preferred for Apple Silicon users?

Thanks for your support, and please let me know if you'd like logs or system diagnostics to help resolve this.

Best regards,
Balraj Singh
official.balraj@gmail.com