Strategy for unmaintained @testing-library/cypress

[MikeMcC399]

What would you like?

Develop strategy to deal with unmaintained repo https://github.com/testing-library/cypress-testing-library

Why is this needed?

• The previous maintainer of https://github.com/testing-library/cypress-testing-library wrote in ci: update validate workflow versions testing-library/cypress-testing-library#289 (review)

  Yeah, there's no active maintainer. Cypress should follow playwright's example and build these queries in as an official part of their API.

with the background information that:

• Repo https://github.com/testing-library/cypress-testing-library is the source of npm package @testing-library/cypress
• Cypress uses @testing-library/cypress as a dependency
• For each major version release of Cypress, the peerDependencies of @testing-library/cypress need to be updated

Other

Consider alternatives:

• Follow the recommendation from @testing-library/cypress and add functionality to Cypress (see ci: update validate workflow versions testing-library/cypress-testing-library#289 (comment))
• Offer to maintain https://github.com/testing-library/cypress-testing-library as-is
• Fork the repo into a Cypress maintained repo
• Remove dependency on @testing-library/cypress
• Delay any decision and take no action

[MikeMcC399]

• There is a reference in Cypress 16: Breaking Changes #33052

[mschile]

PR to loosen the Cypress peer dependency constraint: testing-library/cypress-testing-library#291

[MikeMcC399]

I see also in testing-library/cypress-testing-library#291 (comment) that the offer to pick up the maintenance didn't meet with agreement. They preferred to deprecate the package if possible.

[mschile]

Yep, we plan to have further discussions on how we want to incorporate the plugin, but this will buy us some time in the meantime.