-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
patch-package
not correctly applied since Yarn upgrade
#6582
patch-package
not correctly applied since Yarn upgrade
#6582
Comments
This patch in I believe this is a coincidence though, there is an earlier version of
|
Can we move patch into build step or duplicate it?
…Sent from my iPhone
On Feb 27, 2020, at 12:18, Zach Bloomquist ***@***.***> wrote:
This patch in driver does seem to still be applied correctly in both production and development:
https://github.com/cypress-io/cypress/blob/cb0f32b0b4913cbb403f2e7c51b23ecad50ece9f/packages/driver/patches/sinon+8.1.1.patch#L1-L20
I believe this is a coincidence though, there is an earlier version of sinon installed in the root node_modules which causes this sinon to be installed in the driver folder in both development and production.
node_modules in development and production should probably be aligned and then we can have confidence in where the patches will be applied every time.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I think we just need to add the |
The code for this is done in cypress-io/cypress#6583, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
patch-package
has not been applied to built binaries ever since #5555 was merged, leading to regressions coming from an unpatchedhas-binary2
when users send certain circular data over WebSockets:The patch is correctly applied during development, but during production builds it is not. This is probably because
has-binary2
is innode_modules
in dev, but inpackages/socket/node_modules
in the built binary.The text was updated successfully, but these errors were encountered: