yarn is not installing properly on MacOSX and Windows

[jan-vcapgemini]

Expected behavior

As a devonfw-ide Windows and MacOS user I want to install yarn, so that I can use it for my projects.

Actual behavior

devon yarn is not installed automatically (just with devon yarn setup)

Steps to reproduce (bug) / Use Case of feature request (enhancement)

1. Run devon yarn

Related/Dependent Issues

Comments/Hints:

Affected version:

• OS: Mac, Windows
• devonfw-ide: 2023.07.001-SNAPSHOT

[hohwille]

Please try to include logs, as I could not get what the actual problem was and could not reproduce the bug in the first place.
So here is my log:

hohwille@CE49454 MSYS /d/projects/test2
$ devon yarn
Running: yarn install
/d/projects/test2/scripts/command/yarn: line 84: yarn: command not found
sed: can't read package.json: No such file or directory
No build script is present in package.json - skipping to run build script.

hohwille@CE49454 MSYS /d/projects/test2
$ devon yarn setup
Running: npm install -g yarn@latest

added 1 package in 1s

hohwille@CE49454 MSYS /d/projects/test2
$ devon yarn
Running: yarn install
yarn install v1.22.19
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
Done in 0.05s.
sed: can't read package.json: No such file or directory
No build script is present in package.json - skipping to run build script.

[hohwille]

I am slightly confused why this is happening.
If you call devon yarn with no argument, it will do this:

ide/scripts/src/main/resources/scripts/command/yarn

Line 118 in a66c626

doBuild

This is calling the following:

ide/scripts/src/main/resources/scripts/command/yarn

Line 89 in a66c626

doRunBuild install

And that first calls this:

ide/scripts/src/main/resources/scripts/command/yarn

Line 78 in a66c626

doSetup silent

The actual bug seems to come from this condition:

ide/scripts/src/main/resources/scripts/command/yarn

Line 34 in a66c626

elif [ "${1}" != "silent" ] || [ "${version}" != "latest" ]

Typically the silent argument should only suppress extra log output or extra verbose double checking of the installation.
However, in the current yarn commandlet the installation is simply skipped if the silent argument is provided what is obviously a bug.