HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cypress-io
cypress
TypeScript2017–2024
cypress-io / cypress

cypress

Fast, easy and reliable testing for anything that runs in a browser.

15Distinct people
15Mentions
0Explicit recommenders
51KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Fast, easy and reliable testing for anything that runs in a browser.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:28:55 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year15 dated mentions

Observed mentions: 2017-10-17 14:39:11 UTC to 2024-08-06 16:07:59 UTC.

012342017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC211
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC312
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC110

What Hacker News says

3 sources
As of yesterday Cypress binaries for older versions started blocking third-party plugins, breaking CI for multiple users. It bypasses package.lock and yarn.lock as it downloads a binary from their CDN when installing. See also: https://currents.dev/posts/v13-blocking https://www.cypress.io/blog/2023/11/07/update-defense-intell... https://github.com/cypress-io/cypress/issues/28269 https://github.com/currents-dev/cypress-cloud/issues/193
In Cypress changed older versions to block third-party plugins (ignoring lockfiles)
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 di
Read the rest
srupted 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
In Why Cypress Decided to Block Currents.dev and Sorry Cypress

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.