After xpm install ... --copy shim scripts still point to central store

[TommyMurphyTM1234]

Describe the bug

After a --copy install into an xPack enabled project directory (in which xpm init was previously run) the shim scripts still point to the central store and not to the local copy.

To Reproduce

mkdir test
cd test

xpm init

xpm install @xpack-dev-tools/openocd --copy --verbose
...

type xpacks\.bin\openocd.cmd
@ECHO off
GOTO start
:find_dp0
SET dp0=%~dp0
EXIT /b
:start
SETLOCAL
CALL :find_dp0
"C:\Users\Tommy Murphy\AppData\Roaming\xPacks\@xpack-dev-tools\openocd\0.12.0-3.1\.content\bin\openocd.exe"   %*

Expected behaviour

I presume that shim scripts installed using the --copy option should point to the local copy and not the central store?

Actual behaviour

See above.

Context

• OS Name: Windows 10
• the output of npm doctor

npm doctor
Connecting to the registry
Ok

Checking npm version
Ok
current: v10.8.2, latest: v10.8.2

Checking node version
Ok
current: v20.16.0, recommended: v20.16.0

Checking configured npm registry
Ok
using default registry (https://registry.npmjs.org/)

Checking for git executable in PATH
Ok
C:\Program Files\Git\cmd\git.EXE

Checking for global bin folder in PATH
Ok
C:\Users\Tommy Murphy\AppData\Roaming\npm

Comments

None.