-
Notifications
You must be signed in to change notification settings - Fork 16
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
[email protected] dependency issues deprecation warning #42
Comments
Hi @MikeMcC399 ! Do you know if there are breaking changes in qs going from 6.10.3 -> 6.11.2? I'm also confused why this warning is showing since we are not above 6.10.4 which it suggests to downgrade to in order to avoid the problem. |
Hi Ben @nagash77
I could not see any sign of breaking changes and the tests still pass. However I can't swear that nothing will break! I'm not familiar with the actual contents of
Since If you are concerned about the risks of moving to |
As I was reviewing this, I noticed that
Edit: Except that may not be relevant if they are only devDependencies! Maybe you can get a second opinion about the pros and cons of updating to 6.11.2? Also it seems that npm doesn't try to install the deprecated version, whereas Yarn does, and then complains about it!
|
|
This comment was marked as resolved.
This comment was marked as resolved.
🎉 This issue has been resolved in version 3.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summary
When
@cypress/[email protected]
is installed with Yarn Classic, then the following deprecation notice is output:The deprecation notice is not displayed if npm or pnpm is used to install
@cypress/[email protected]
. This is because these other package managers prefer non-deprecated versions to deprecated versions and therefore they select the alternative, non-deprecated,[email protected]
version instead of selecting the deprecated[email protected]
version.Simplest Example to Reproduce
Expected behavior
When
@cypress/request
is installed using Yarn, then no deprecation notice should be displayed.Possible solution
The warning suggests:
see
qs
CHANGELOGContext
[]
is appended on single-item arrays. Upgrade to v6.11.0 or downgrade to v6.10.4 to fix. cypress#27644 as a concern.Your Environment
Logs
Notes
cypress-io/request
is configured with"qs": "~6.10.3"
request/package.json
Line 43 in 99338c8
npm view [email protected]
shows the deprecation noticeThis is a deprecation notice, not a vulnerability warning. There are currently no vulnerabilities detected in
@cypress/request
:The text was updated successfully, but these errors were encountered: