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