Consider adding `cross-env` as devDependencies for better development experience

Is your feature request related to a problem? Please describe. storybook script requires you to set environment variables called STORYBOOK_VUE_DEV_TOOLS. Unfortunately, npm scripts cannot set environment variables on Windows.

To solve this issue, I suggest adding cross-env before setting the environment variables. cross-env works on Windows, Linux, and macOS.

[Namchee]

I haven’t tried WSL2 yet since I have bad experiences from WSL. I’ll give it a shot later.

Nonetheless, I’ll create a pull request to address this issue as cross-env ensures maximum compatibility in most machines.

[wopian]

and I don’t think its a good idea to develop sth on windows. I suggest using something like WSL 2 for better dev experience.

That statement simply hasn’t been true for the last 10 years. There are some low-level differences if you’re interacting with the shell languages directly, like how Windows’ PowerShell and the many *nix’s shell variants use a different syntax for environment variables but that and others are easily handleable.

There’s nothing wrong with developing on Windows without WSL(2) - it has excellent dev tooling and support like any other OS.