-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: patterns.reduce is not a function #404
Comments
I also came across this problem but infact it was an error from my side as in the |
I am facing this error too. Until this is resolved, workaround is to fixate to particular version in "resolutions": {
"fast-glob": ">=3.2.9 <=3.2.12"
} |
The public interface of this package does not support a string as the value for the Right now the problem needs to be fixed on the cypress side. Similar issues: #403 |
Thanks @mrmlnc , looking into a fix: cypress-io/cypress#27231 |
Thanks all! Since this is a cypress-side issue, I'll close this out and watch for an update on the ticket @samtsai mentioned |
Why is this a cypress-side issue? I have the same issue in a project that has nothing to to with cypress. So I would assume that Version 3.3.0 has an issue here. Can we reopen this? |
This is not a cypress problem. It is the problem of every package that does not respect the public interface of that package. The public interface of this package does not support a string as the value for the I am willing to modify the public interface if the number of affected packages reaches dozens. For now, I prefer to keep the current implementation for codebase cleanliness. |
Technically I'm on your side, but it breaks stuff with a minor version. That's usually not how it should work. According to Semver a minor version should a minor version »add functionality in a backward compatible manner«. That's not the case here. So technically this should be 4.0.0. But I totally understand that's not your fault, that other packages use your package in a wrong way. |
That sounds pretty compelling to me. I plan to fix this issue and postpone the major change to the next major release. |
Environment
Actual behavior
TypeError thrown starting today after Node and package updates
Expected behavior
No error
Steps to reproduce
Code sample
This is our cypress.config.js:
Error Details
Stack trace
The text was updated successfully, but these errors were encountered: