Description:
The published VSIX file for TheCaffinatedDeveloper.gorules-vscode v0.0.2 was packaged on an Apple Silicon machine (darwin-arm64) and only bundles that specific native binary inside its production node_modules layer.
Because VS Code extensions are unzipped on client machines without running an active npm install cycle, the runtime engine crashes on activation for non-macOS users when trying to resolve require('@gorules/zen-engine-win32-x64-msvc') (or the equivalent Linux GNU targets).
Steps to Reproduce:
- Install extension v0.0.2 on a Windows x64 machine.
- Open a
.jdm.json file and toggle to the JDM Editor view.
- The panel remains an empty, unresponsive webview shell due to activation failure.
Proposed Resolution:
Update the vsce package deployment CI/CD workflow script to ensure that all native NAPI-RS target binaries for required environments (win32-x64, linux-x64, darwin-x64) are bundled explicitly into the extension payload prior to distribution.
Description:
The published VSIX file for
TheCaffinatedDeveloper.gorules-vscode v0.0.2was packaged on an Apple Silicon machine (darwin-arm64) and only bundles that specific native binary inside its productionnode_moduleslayer.Because VS Code extensions are unzipped on client machines without running an active
npm installcycle, the runtime engine crashes on activation for non-macOS users when trying to resolverequire('@gorules/zen-engine-win32-x64-msvc')(or the equivalent Linux GNU targets).Steps to Reproduce:
.jdm.jsonfile and toggle to the JDM Editor view.Proposed Resolution:
Update the
vsce packagedeployment CI/CD workflow script to ensure that all native NAPI-RS target binaries for required environments (win32-x64,linux-x64,darwin-x64) are bundled explicitly into the extension payload prior to distribution.