Thanks for sharing your concerns, Jessica, we tried to be fully transparent and share our findings with the interested audience. I have added a disclaimer that explicitly mentions the owners of the packages to avoid confusion.
- The article clearly states what entities are affected - Currents, Sorry Cypress and Deploy Sentinel; it doesn't claim those are random package authors.
- Not all the listed packages are written by the dude or written and _THEN_ forked, we provided a detailed breakdown of each package origin. For example, @deploysentinel/cypress-debugger is a completely standalone, innovative software released more than a year before Cypress Test Replay and cypress-debugger
- The article lists all the blocked packages we were able to discover. We published the full list to be totally transparent. Obviously, we create and work on cypress-related packages - e.g. a vscode extension for cypress. There was also a rename from Cypress Dashboard to Cypress Cloud. NPM lists ~1.6K packages with "cypress-" prefix. Another example: we ran a survey on a community Slack channel with ~500 members to pick a name for cypress-debugger - the options were: cypress-debugger, cypress-debug, cypress-tracer; cypress-debugger won.
An interesting experiment would be to rename those packages. Do you believe they will be unblocked?
A free plugin to record everything that’s happening during Cypress test runs - browser logs, network events, DOM changes and replaying in a web player. It’s like Playwright Traces but for Cypress - convenient for debugging failed CI runs.
Sorry for the shameless plug :) We have also been working for a while on time travelling. Hoping to share some results soon - your work is very inspiring.
Great to see such a variety of tools that make CI testing less painful!
- Revenue: get 150 customers paying at least $66/mo RECURRING
- Market: choose a BIG market, build a product that people need and is naturally recurring
- Customer acquisition: ads > content. It's more reliable
I have been doing open-source cypress tests dashboard (sorry-cypress) for more than 2 years. It's been used by big names, saving $$$ for those companies.
Now I have launched https://currents.dev, which is based on (MIT-licensed) sorry-cypress, which resembles (paid) Cypress Dashboard, that monetizes (MIT-licensed) cypress tests runner.
I have been doing open-source cypress tests dashboard (sorry-cypress) for more than 2 years.
Now I have launched https://currents.dev, which is based on (MIT-licensed) sorry-cypress, which resembles (paid) Cypress Dashboard, that monetizes (MIT-licensed cypress tests runner.
- The article clearly states what entities are affected - Currents, Sorry Cypress and Deploy Sentinel; it doesn't claim those are random package authors.
- Not all the listed packages are written by the dude or written and _THEN_ forked, we provided a detailed breakdown of each package origin. For example, @deploysentinel/cypress-debugger is a completely standalone, innovative software released more than a year before Cypress Test Replay and cypress-debugger
- The article lists all the blocked packages we were able to discover. We published the full list to be totally transparent. Obviously, we create and work on cypress-related packages - e.g. a vscode extension for cypress. There was also a rename from Cypress Dashboard to Cypress Cloud. NPM lists ~1.6K packages with "cypress-" prefix. Another example: we ran a survey on a community Slack channel with ~500 members to pick a name for cypress-debugger - the options were: cypress-debugger, cypress-debug, cypress-tracer; cypress-debugger won.
An interesting experiment would be to rename those packages. Do you believe they will be unblocked?