[Bug?]: yarn global command giving "No project found" error

[DrakaSAN]

Self-service

• I'd be willing to implement a fix

Describe the bug

On Debian 10 (stable)

Installed yarn via corepack enable, whatever yarn global command launched ends with an Usage Error:

$ yarn --version
3.2.1

$ yarn global bin
Usage Error: No project found in /home/user

$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] <scriptName> ...
$ yarn global 
Usage Error: No project found in /home/user

$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] <scriptName> ...

To reproduce

$ corepack enable
$ yarn global bin

Environment

System:
    OS: Linux 4.19 Debian GNU/Linux 10 (buster) 10 (buster)
    CPU: (4) x64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
  Binaries:
    Node: 16.13.1 - /tmp/xfs-5ffd854a/node
    Yarn: 3.2.1 - /tmp/xfs-5ffd854a/yarn

Additional context

I guess something is wrong in my environment, but as a newcomer to yarn I'm don't know where to look. This looks like the global command do not have its repository setup correctly, which if I knew where to look, I maybe could gather more info, but since even yarn global bin ends in error, I'm stuck.

Using corepack prepare doesn't seems to change anything

$ corepack prepare yarn@3.2.1 --activate
Preparing yarn@3.2.1 for immediate activation...
$ yarn global bin
Usage Error: No project found in /home/user

$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] <scriptName> ...

[DrakaSAN]

Looks like yarn doesn't have global anymore which explain why this is failing

[arcanis]

Indeed, it suggests yarn dlx instead, or to use npm for global binaries (Yarn now focuses exclusively on project management, not system management).