Extension fails to activate: Cannot find module 'npm-which' due to private npm registry

[tomereli]

On macOS, with the Bash Debug extension installed, the extension fails to activate with the following error:

Attempts to install npm-which globally fail because my npm is configured to use a corp registry, which does not host all public npm packages. Due to company security policy, I cannot change this registry or install global packages from the public npm registry.

Steps to reproduce:

1. Use a corporate/private npm registry that does not proxy public npm packages.
2. Install Bash Debug extension in VS Code.
3. Attempt to start a debug session for a bash script.

Expected behavior:
The extension should activate and allow debugging.

Actual behavior:
The extension fails to activate due to missing npm-which dependency.

Additional context:

• macOS, VS Code latest, Bash Debug v0.3.9
• Company policy prevents installing global npm packages from the public registry.
• The extension should ideally bundle all required dependencies or not require global npm modules.

Workarounds tried:

• Attempted to install npm-which globally (blocked by private registry).
• Reinstalled extension and VS Code.

Request:
Please consider bundling all required dependencies with the extension, or provide a way to work without requiring global npm modules, to support users in restricted/corporate environments.