-
Notifications
You must be signed in to change notification settings - Fork 133
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
Why is query-string fixed to v5? This cause multiple query string in my final webapp bundle #548
Comments
Hi @kopax-polyconseil |
Thanks for your reply, problem here is that those package are not maintained anymore, perhaps an upgrade of the deps on all the dep tree would be the right move ? There's a reason why new versions come out, I hope you know it. |
@yuhao900914 also we use yarn, and
|
Hi @kopax-polyconseil The query-string@5 to the latest version has breaking changes. To support the older browser, we need to use query-string@5. |
Thanks for your reply, on a big project like ours I manage to solve the dedupe of this problem using webpack resolve alias, and I will have another try using the resolution :) |
Snyk jobs are now failing in our pipelines because of a downstream DoS vulnerability coming from a dependency in This has been fixed in |
same issue at 8.21.4, setting "amplitude-js": "8.21.3" in package.json removes the error |
Expected Behavior
I expect one query-string module in my final web app bundle
Current Behavior
strict-uri-encode (Found 2 resolved, 2 installed, 2 depended. Latest 2.0.0.)
1.1.0 ~/strict-uri-encode
[email protected] -> amplitude-js@^8.16.1 -> query-string@5 -> strict-uri-encode@^1.0.0
2.0.0
/@react-navigation/core//strict-uri-encode[email protected] -> @react-navigation/native@^6.0.6 -> @react-navigation/core@^6.1.0 -> query-string@^7.0.0 -> strict-uri-encode@^2.0.0
Possible Solution
Do not fix query string version and upgrade it to latest
Steps to Reproduce
Not necessary
Environment
The text was updated successfully, but these errors were encountered: