CT Devservers should support instrumenting code coverage as a baked in option

[sync-by-unito]

Summary

Currently we’re using a plugin (instrument-cra) to do this, but we could build first class support into the devservers directly that automatically instruments the code and generates code coverage reports.

┆Issue is synchronized with this Jira Task by Unito
┆author: Brian Mann
┆epic: CT Architecture
┆friendlyId: UNIFY-1701
┆priority: Low
┆sprint: Backlog
┆taskType: Task

[sync-by-unito]

➤ Jennifer Shehane commented:

Brian Mann Would this change affect users or is this just a code refactor?

[lmiller1990]

Related: cypress-io/cypress-documentation#5519

Integrating this to all our supported framework/bunlder combos would be a big project. For now, we are going to document how to set it up for known configurations in cypress-io/cypress-documentation#5519. We can revisit this in the future, if we decide we'd like first class support. This would mean shipping istanbul and the associated plugins in the binary.

[lmiller1990]

This is way out of scope for the current state of things - I'd be happy to see this documented in cypress-io/cypress-documentation#5519.

If we do revisit this as an initiative, we will make a new Epic with the associated tickets, following our internal process for project work.