[v2] Windows PowerShell CLI resolves the removed v1 bin path

[mynameistito]

Automatically submitted on behalf of the user by an AI agent.

Bug

After upgrading the local executor package from v1.6.10 to v2.0.0-beta.7, running executor in PowerShell fails. Node tries to load the old v1 entry point at .../node_modules/executor/bin/executor, which does not exist in v2. The v2 package declares bin.mjs as its CLI entry point.

Observed error:

Error: Cannot find module '.../node_modules/executor/bin/executor'
code: 'MODULE_NOT_FOUND'
Node.js v26.10.0

The package-local Windows launcher (node_modules/.bin/executor.exe --version) reports executor v2.0.0-beta.7, but bare executor --version in PowerShell fails with the module-not-found error. This appears to be a stale or incompatible command shim still targeting the v1 path.

Expected

The installed executor command should launch the v2 bin.mjs entry point cleanly, or fail with a clear install/shim diagnostic instead of attempting to load the removed v1 path.

Environment

• Windows 11 Pro, x64 (build 10.0.26300)
• PowerShell 7.6.6
• Node.js v26.10.0
• Bun 1.4.2
• executor package v2.0.0-beta.7, upgraded from v1.6.10

Reproduction

1. Upgrade the local executor package from v1.6.10 to v2.0.0-beta.7.
2. From PowerShell in the package directory, run executor --version.
3. Node attempts to load node_modules/executor/bin/executor and exits with MODULE_NOT_FOUND.

Before you submit

• I searched the existing issues for this Windows/PowerShell CLI entry-point error and did not find a duplicate.

[mynameistito]

Follow-up: On this Windows install, Get-Command executor resolved to Bun’s global shim, not the package-local launcher. The package-local v2 launcher worked. Reinstalling the global CLI with bun add --global --exact executor@2.0.0-beta.7 replaced the stale shim, and bare executor --version now works. The issue may be specific to a stale Bun global shim rather than the package-local upgrade path; I’ve updated the local install and can no longer reproduce it.