"npx sb" fails on Windows

tldr;

Affects Windows OS users who wants to report (here) a new issue and follow the template instructions

---

Hi, I wanted to open an issue and found myself opening this issue first because I’ve followed the instructions below on my Windows 10 (Terminal ran as admin) and had gotten an error:

Please create a reproduction by running npx sb@next repro

Result:

🏃 Starting for react latest

🏗 Bootstrapping react project (this might take a few minutes)
mkdir react && cd react && touch yarn.lock && yarn init --yes && yarn add react react-dom
'touch' is not recognized as an internal or external command,
operable program or batch file.
An error occurred while executing: `mkdir react && cd react && touch yarn.lock && yarn init --yes && yarn add react react-dom`
🚨 Bootstrapping react failed
🚨 Failed to create repro
Error: Error: command exited with code: 1:
    at repro (C:\Users\Yaire\.pnpm-store\v3\tmp\_npx\22952\5\node_modules\.pnpm\@storybook+cli@6.5.0-alpha.55\node_modules\@storybook\cli\dist\cjs\repro.js:172:11)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

Windows doesn’t have touch command so I found a workaround

I also have tried to install yarn and now it works. (Why yarn and not pnpm…)

---

I suggest these things be mentioned as hard requirements prior to running the npx sb@next repro command on Windows

[IanVS]

@vladgorbachev there are some changes in 7.0 to the way storybook is run. You can check out https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#from-version-65x-to-700, and can also run npx sb@future automigrate to handle most of the changes from 6.5 to 7.0.

[vladgorbachev]

npx sb upgrade --prerelease but after

'start-storybook' is not recognized as an internal or external command,

alpha31, react 18.2.0