[Content]: yarn create command doesn't work on macOS

[Neighborkid01]

📚 Subject area/topic

/solid-start/getting-started.mdx

📋 Page(s) affected (or suggested, for new content)

https://docs.solidjs.com/solid-start/getting-started

📋 Description of content that is out-of-date or incorrect

$ yarn create solid@latest
yarn create v1.22.22
(node:39466) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...

success Installed "create-solid@0.7.0" with binaries:
      - create-solid
/bin/sh: /opt/homebrew/bin/create-solid@latest: No such file or directory
error Command failed.
Exit code: 127
Command: /opt/homebrew/bin/create-solid@latest
Arguments: 
Directory: /Users/my_user/Documents/GitHub
Output:

info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.

🖥️ Reproduction in StackBlitz (if reporting incorrect content or code samples)

No response

[LadyBluenotes]

@atilafassina do you know why this is?

[atilafassina]

@atilafassina do you know why this is?

@LadyBluenotes
yarn create works by installing create- and then running the binary. When you write yarn create solid@latest, yarn installs create-solid@latest correctly, but then tries to execute a binary literally named create-solid@latest — instead of just create-solid.
It's a quirk in how yarn create resolves the binary name: it naively appends @latest to the binary path rather than stripping the version specifier before looking up the executable.

We should change our command to just yarn create solid

---

though @Neighborkid01 Yarn 1.22 is very old, deprecated, and unsupported.
For using Yarn in a project you're better off upgrading to 4.x.x
But the Yarn team recommends versioning Yarn per-project, so the recommended way is using corepack... causing this chicken and egg problem (need to run create with a very very old binary so you have a project, so you can update the binary)... or update your global $PATH somehow