can I use CLI tools like create-react-app to start a new project with modern yarn, no migration?

[kay-o]

Can I use CLI tools like create-react-app to start a new project with modern yarn, no migration?

If I follow Yarn 'getting started' instructions and want to create a new react app, as best I can understand I have to go through installing in Yarn 1, then migrating. Is that my best option or is there a more direct alternative?

The more important question: if I want the headline benefits of Yarn 2 like Zero-installs and Plug-n-Play, what are the minimal reliable steps for getting there? Ideally instructions serve just as a minimalist reminder of step 1, step 2, step 3, ... step n.

A while back I "read the manual" thoroughly, cheering as I did, and I successfully started "modern yarn" projects soon after said thorough reading. Now when I return to the Getting Started docs, hoping not to do another thorough reading, I simply can't make headway. (The docs contain boatloads of info, and the actual steps are challenging to extract, even if you've extracted them in the past).

[kay-o]

Here's the approach I'm using currently. I've tried several options. None seems likely to be the 'supported' approach. I'll note this one as a reminder to myself, and for anyone who finds it useful. It seems to be smoother and easier to remember than the alternatives I've tried.

$ cd { path of the project's intended parent directory } # change to a directory level above the intended project directory
$ yarn set version stable # update yarn to a modern version for this dir and its subdirs in place of the yarn classic version installed on my system
➤ YN0000: Retrieving https://repo.yarnpkg.com/3.2.2/packages/yarnpkg-cli/bin/yarn.js
➤ YN0000: Saving the new release in .yarn/releases/yarn-3.2.2.cjs
➤ YN0000: Done in 0s 760ms
$ rm package.json # indicate this parent directory is not part of a project
$ yarn dlx create-react-app my-app # use the cli tool of your chosen framework to kick off your new project
[... follow prompts to create new project ...]
$ cd { path of new project directory }
$ yarn set version stable # ensure the yarn version designation is saved in your project repository

Note the repetition of yarn set version stable and the slight, but important, differences in both the reason for doing so and the location in which to run each instance.