yarn installed rvm-windows fails with missing AppData\Local\Yarn\bin\rvm.ps1 whereas npm based installation works

[cbroult]

While following the installation procedure https://github.com/magynhard/rvm-windows?tab=readme-ov-file#installation

I selected the use of yarn and got the following error:

rvm list known
C:\Users\cbrou\AppData\Local\Yarn\Data\global\node_modules\rvm-windows\src\cli\tasks\_init.js:132
            throw new Error(`Could not find file '${file}'`);
            ^

Error: Could not find file 'C:\Users\cbrou\AppData\Local\Yarn\bin\rvm.ps1'
    at RvmCliInit._writeToSecondLine (C:\Users\cbrou\AppData\Local\Yarn\Data\global\node_modules\rvm-windows\src\cli\tasks\_init.js:132:19)
    at RvmCliInit.initSessionToRvmExes (C:\Users\cbrou\AppData\Local\Yarn\Data\global\node_modules\rvm-windows\src\cli\tasks\_init.js:82:18)
    at Object.<anonymous> (C:\Users\cbrou\AppData\Local\Yarn\Data\global\node_modules\rvm-windows\src\cli\cli.js:24:12)
    at Module._compile (node:internal/modules/cjs/loader:1740:14)
    at Object..js (node:internal/modules/cjs/loader:1905:10)
    at Module.load (node:internal/modules/cjs/loader:1474:32)
    at Function._load (node:internal/modules/cjs/loader:1286:12)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:234:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:151:5)

Node.js v23.5.0
PS C:\Users\cbrou> 

Switching to the npm based installation, I was able to successfully install ruby 3.4.1.

PS C:\Users\cbrou> npm -v
10.9.2
PS C:\Users\cbrou> node -v
v23.5.0
PS C:\Users\cbrou> yarn -v
1.22.22
PS C:\Users\cbrou> rvm -v
rvm-windows 1.0.0
PS C:\Users\cbrou> rvm list
=* ruby-3.4.1

# => - current
# =* - current && default
#  * - default
PS C:\Users\cbrou>

What should I do to understand what I am doing wrong?

[magynhard]

Hi @cbroult , thank you for your feedback.

I will check this soon and try to reproduce.

[cbroult]

I am happy to try it again if you need support to reproduce it or confirm it as a user error on my side.

[magynhard]

I digged in deeper.

Yarn does not create PowerShell files for global installs on its own. As I do not use PowerShell at all, i missed to test this case again with yarn.

I tried to find to make yarn compatible.

So i added a post install script for yarn, doing so manually by using a template from npm.
But then i figured out, that yarn and npm have very different behaviours of character encodings / charsets which cause errors on paths using special characters. They are not compatible and i would need to create and handle different encodings for npm and yarn.

So i decided to officially cancel installation support for yarn, as this might need too much special maintenance.

Thank you very much for your feedback to figure out this.