what's the logic on project admin-build using yarn instead of npm?

[0x4]

Question

I had trouble running shopware-cli project admin-build because one of the store-plugins installed with composer contained a yarn.lock file.
looks like admin-build uses yarn inside the plugin directory if a yarn.lock file is found?
is there a way to force npm? or at least fall back to npm if yarn fails? afaik yarn is not a requirement for shopware

in my case: using bin/build-administration.sh works
issue1: if yarn is not installed admin-build failes
issue2: that yarn.lock was malformed - so even if installing yarn the build failes - and because the yarn.lock file is from an external dependency the fix delting the yarn.lock file is not the best option

[shyim]

Is yarn not installed or does it really yarn fail?

The problem with running npm is that the yarn.lock does nothing and maybe newer packages will be installed

[0x4]

yarn was not installed - in this case admin-build stopped with an error that yarn is missing

after installing it I had an issue with the yarn file in that plugin

error SyntaxError: Invalid value type 1283:0 in ...src/Resources/app/administration/yarn.lock

looks like an error in the plugin - or version mismatch with yarn (i'm not really a node expert)

btw. that plugin has a package-lock.json and a yarn.lock included

main question: the "normal" way using bin/build-administration.sh only uses npm afaik - so for consistency it should be better using the same logic in shopware-cli? if the plugin manufacturer is using yarn only that wouldn't work in the default way?