Incorrect behaviour of `basetag rebase` on Windows

[rngnrs]

Expected Behavior

$ pnpm basetag rebase

# app\common\domain\errors\index.js
  ../../infrastructure/Config.js -> $/app/common/infrastructure/Config.js

# app\common\infrastructure\Config.js
  ../../../package.json" assert { type: "json -> $/package.json" assert { type: "json
...

Current Behavior

$ pnpm basetag rebase

# app\common\domain\errors\index.js
  ../../infrastructure/Config.js -> $\app\common\infrastructure\Config.js

# app\common\infrastructure\Config.js
  ../../../package.json" assert { type: "json -> $\package.json" assert { type: "json
...

Problem description

rebase should use / path separator in require/import statements. \, aka Windows path.sep, means escaping symbols in this case. It leads to such an error:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '$appcommoninfrastructureConfig.js'...

Possible solution

Replace \ to / in pkgPath variable forcibly.

Environment

• basetag 2.1.0
• node 18.14.0
• pnpm 8.2.0
• Win 10