querystring (introduced through URL) is obsolete
See original GitHub issueCurrent behavior
While installing cypress 9.0.0, a warning shows up indicating querystring is no longer used.
Debug logs
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
Cypress Version
9.0.0
Package Manager
npm
Operating system
Linux
Other
This is the dependency tree:
└─┬ cypress@9.0.0
└─┬ url@0.11.0
└── querystring@0.2.0
url seems also in the brink of obsolescence, having been released 6 years ago.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Is the querystring trick obsolete? - Stack Overflow
The trick isn't obsolete as browsers still have no way of knowing the file has been modified without requesting it, this is just...
Read more >How to migrate from querystring to URLSearchParams in ...
Old code using querystring can easily be migrated to URLSearchParams using this guide.
Read more >URI.escape is obsolete. Percent-encoding your query string
Ruby 2.7.0 shows a warning when invoking URI.escape or its alias, URI.encode . It might look like a fresh deprecation, but the fact...
Read more >obsolete umbpage querystring parameter and urlrewriting rules
Using Umbraco And Getting Started. Umbraco 6. Today a couple of days before upgrade Umbraco from 4.7.1 to 6.2.6 I found that my...
Read more >Query string - Wikipedia
In cases where special logic is invoked, the query string will be available to that logic for use in its processing, along with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Maybe we can change usage of
url
toquerystringify
since it’s not depracated and does similar thing?@jennifer-shehane Realistically I think it’s an issue external to Cypress so nothing more than that. But the details are:
When tests are run as part of our Appveyor build via a powershell build script the warnings are interpreted as breaking errors
The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
I changed the ErrorActionPreference and strictly they are warnings so it shouldn’t be stopping probably but in any case would be helpful to get these warnings removed.