fix: #22002 choikdar ignore EPERM issues

[tgriesser]

• Closes Cypress v10 crashes with EPERM error #22002

User facing changelog

Consistently handle EPERM issues in chokidar watching

Additional details

Steps to test

How has the user experience changed?

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)
• Has a PR for user-facing changes been opened in cypress-documentation?
• 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.

[flotwig]

Is there a way we can lint for this or otherwise enforce this? Otherwise this will regress next time someone adds a chokidar.watch.

Could wrap chokidar in a function that always passes ignorePermissionErrors

[cypress]

---

Test summary

37553 • 0 • 454 • 0 • 2

---

Run details

Project	cypress
Status	Passed
Commit	3bdaada
Started	Jun 1, 2022 8:25 PM
Ended	Jun 1, 2022 8:41 PM
Duration	15:31 💡
OS	Linux Debian - 10.11
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	cypress/e2e/cypress/proxy-logging.cy.ts		2
1	Proxy Logging > request logging > xhr log has response body/status code when xhr response is logged second
2	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

[tgriesser]

Is there a way we can lint for this or otherwise enforce this? Otherwise this will regress next time someone adds a chokidar.watch.

@flotwig yeah definitely something we should look into for the future, in the meantime let's just go with this change for now

[cypress-bot]

Released in 10.0.1.

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