chore: fix initial installation on windows

[userquin]

Context

After following the CONTRIBUTING.md guide, there are still errors running certain packages while developing in the Cypress repo on a Windows machine.

How to test

1. Follow the CONTRIBUTING.md guide
2. Run yarn and install deps from the root directory of the project.

Current Behavior

When running yarn from the root once installed node and python there are errors.

There are scripts running yarn <node_modules/.bin/command> ...args commands, and they will fail on windows since they resolve to <node_modules/.bin/command> instead <node_modules/.bin/command.cmd>.

For example, on npm/vue we got this error:

@packages/electron: Packaging app for platform win32 x64 using electron v13.2.0
cypress: exec babel index.js -o build/index.js
@cypress/vue: /usr/bin/bash: F:workprojectsquiniGitHubcypress-developmentnode_modules.binrollup: command not found
@cypress/vue: error Command failed with exit code 127.
@cypress/vue: error Command failed with exit code 127.
lerna ERR! yarn run build exited 127 in '@cypress/vue'
lerna WARN complete Waiting for 5 child processes to exit. CTRL-C to exit immediately.

New Behavior

• It doesn't crash on windows.
• You can run the Cypress build tasks.

Tests

N/A

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[CLAassistant]

All committers have signed the CLA.

[userquin]

As a reminder, do not use yarn to execute binaries since it will break executions on windows, use the binary directly.

For example, reviewing the unified-desktop-gui branch about using unplugin-icons, you were using yarn vite dev and yarn vite build instead creating/updating a new script using directly vite:

"scripts": {
  "vite:dev": "vite",
  "vite:build": "vite build",
  "vite:preview": "yarn vite:build && vite preview"
}

You're using vite when building for production: "build-prod": "cross-env NODE_ENV=production vite build" .

[JessicaSachs]

I'm not sure about the need for npm/create-cypress-tests/scripts/copy-templates.js. Can we use an existing library?

[JessicaSachs]

Hmm, there has to be an easier way, right? Why is copy-templates necessary? Will something like this work?

[userquin]

just try build the scope

[JessicaSachs]

We spoke about this again, and we currently actually have no pattern within the build scripts for copying globbed files. (super weird). The other place we copy files within the scripts directory doesn't handle globs and isn't that pretty.

This fixes some windows development environments, so I think it's good to merge.