fix: sanitize internal vite plugins

[ZachJW34]

• Closes @cypress/vite-dev-server returns stubbed out vite plugin function when not in DEBUG and conflicts with vite-ssr plugin. #22021

User facing changelog

Vite dev-server for component testing will not crash if user has vite plugins that rely on non-empty plugins list

Additional details

Vite expects registered plugins to match a certain shape. We were pushing a null value into the plugins list if the user did not enable CYPRESS_INTERNAL_VITE_INSPECT or did not have vite-plugin-inspect installed. This PR filters the list of plugins we add to exclude any null values.

Also added a fallback for if the require of the plugin doesn't have a default property, as testing locally a node require of vite-plugin-inspect was returning the function.

Added unit testing to npm/vite-dev-server. We were running the vite cypress integration tests twice on CI since their is an explicit job for running the integration tests in the circle.yml and the package had a test script that pointed to the integration tests. I swapped the test script to only run the newly added unit tests.

Steps to test

See original issue

How has the user experience changed?

na

PR Tasks

• Have tests been added/updated?
• Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[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.

[marktnoonan]

I see a failure on https://app.circleci.com/pipelines/github/cypress-io/cypress/38902/workflows/30f43bec-0c32-4cfd-82c3-f8fad4416773/jobs/1582942 but it looks Percy-related. I don't think we are using percy in these e2e tests at the moment, going to take a closer look at what's going on there.

[cypress]

---

Test summary

4876 • 0 • 59 • 0 • 1

---

Run details

Project	cypress
Status	Passed
Commit	0d4f040
Started	Jun 2, 2022 8:22 PM
Ended	Jun 2, 2022 8:37 PM
Duration	15:07 💡
OS	Linux Debian - 10.11
Browser	Electron 100

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/e2e/cypress/proxy-logging.cy.ts		1
1	Proxy Logging > request logging > xhr log has response body/status code when xhr response is logged second

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard

[marktnoonan]

🎉 I am on this branch and was able to open the packages/vuetify project in https://github.com/vuetifyjs/vuetify/tree/next in global mode without hitting the error this time. Percy CI issues can wait.

[cypress-bot]

Released in 10.0.2.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v10.0.2, please open a new issue.