Mike McCready

@tik9 > Should I execute the code on top `mkdir serve-test..` and then execute the workaround? You would replace `serve-test` with the name of your existing repository. Sorry if that...

- Re-submitted as issue #802 Node.js 21 is now in maintenance and reaches [end-of-life](https://github.com/nodejs/release#release-schedule) on June 1, 2024.

@JohnKalan > I can change the list making the corresponding additions and removals. I would like to be assigned and procide in opening a pull request. This change cannot be...

@JohnKalan We just have to wait until somebody from the Cypress.io team can pick this up. Although it is an easy change it is low priority.

Depending on the criteria for keeping deprecated plugins displayed in the list and therefore the number of plugins in this category, it might be better to introduce a `deprecated` badge...

This issue was assigned to Ely who left the organization. The issue is still very relevant and it needs some management decisions from the Cypress team. What is the compatibility...

I thought I might at least be able to get rid of the `debug` deprecation, however updating to the current `[email protected]` causes major changes in `package-lock.json`. Even without attempting to...

Hi Ben @nagash77 This is quite a tricky issue, so I wasn't expecting it to get solved soon, and I'm not even sure that it can be solved in Cypress...

- https://github.com/netlify/cli/issues/5323 is an open issue regarding the `EBADPLATFORM` error. - A workaround is to revert to netlify-cli@[12.2.8 ](https://github.com/netlify/cli/releases/tag/v12.2.8) (which however causes a page full of deprecation warnings etc.)

[`netlify-cli` v14](https://github.com/netlify/cli/releases/tag/v14.0.0) has been released. Edit: Latest version is now `v17`. This can unblock steps needed to resolve this issue, however there are still multiple deprecation warnings and critical vulnerabilities...