I disagree with the assertion that creating npm packages that interact with cypress is brand squatting. Names prefixed with the target ecosystem are common for discoverability and context.
Trademark law prevents competitors from using another company's name and brand in a confusing way, but some reference is often needed to identify compatibility.
Competition is healthy, and this feels like a much larger company taking increasingly aggressive moves towards a competitor who has created a superior hosted product in the same ecosystem.
In transparency, we were using Cypress Enterprise, were frustrated with their lack of responsiveness to product suggestions and support requests and rapidly increasing costs. We switched to Currents and have been much happier with the speed, quality of product, responsiveness, and cost. We were impacted and disrupted by yesterday's sudden blocking of v12, which occurred without explicit notification despite our Cypress accounts. Currents now provides alternative Cypress Binaries - https://currents.dev/readme/integration-with-cypress/alterna...
Fortunately, we've been migrating to Playwright, which Currents has supported as of this year. This accelerates the need.
Edit: There's a GitHub issue opened by others impacted, including people who had considered getting paid Cypress support until the unilateral blocking - https://github.com/cypress-io/cypress/issues/28269
I agree! Thanks for posting the link to Github issue, I was looking for one to also voice my thoughts. We are also one of the companies affected and I just spent the entire day researching alternatives and planning future moves.
For now we'll unblock ourselves with the modified binaries workaround, but who knows when we'll get blocked without any warning again? Unfortunately migrating to something else will not be easy for us (over 1.2k complex test cases written in 200+ spec files). In the meantime we'll probably have to limit number of tests runs and migrate to Cypress.io before we do any moves towards Playwright.
I'd love to hear your thoughts on Playwright. I constantly hear amazing things about it and there are issues with Cypress that really frustrate me (ekhem Cypress.Chainable...). Have you encountered any significant flake with Playwright? How easy it is to debug and solve?
Briefly, we've found Playwright to be easier to implement (exception: Vue and component testing which is functional, but experimental and not well documented), easier to target, faster, and less flaky.
FWIW, GitHub Copilot is great at helping refactor tests.
Trademark law prevents competitors from using another company's name and brand in a confusing way, but some reference is often needed to identify compatibility.
Competition is healthy, and this feels like a much larger company taking increasingly aggressive moves towards a competitor who has created a superior hosted product in the same ecosystem.
In transparency, we were using Cypress Enterprise, were frustrated with their lack of responsiveness to product suggestions and support requests and rapidly increasing costs. We switched to Currents and have been much happier with the speed, quality of product, responsiveness, and cost. We were impacted and disrupted by yesterday's sudden blocking of v12, which occurred without explicit notification despite our Cypress accounts. Currents now provides alternative Cypress Binaries - https://currents.dev/readme/integration-with-cypress/alterna...
Fortunately, we've been migrating to Playwright, which Currents has supported as of this year. This accelerates the need.
Edit: There's a GitHub issue opened by others impacted, including people who had considered getting paid Cypress support until the unilateral blocking - https://github.com/cypress-io/cypress/issues/28269