The querystring package is deprecated
See original GitHub issue- Laravel Mix Version: 6.0.43
- Node Version (
node -v
): 17.8.0 - NPM Version (
npm -v
): 8.5.5 - OS: Windows 11
Description:
When installing Laravel Mix, the following message appears (due to the use of node-libs-browser, which is also deprecated):
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
Steps To Reproduce:
npm install laravel-mix
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:5
Top Results From Across the Web
querystring dependency is deprecated · Issue #3862 - GitHub
Webpack-dev-server 4.2.1 depends on url 0.11.0. This package hasn't had a release in 6 years. It in turn depends on querystring ^0.2.0.
Read more >React npm warn deprecates how to deal with it?
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN ...
Read more >querystring - npm
This package has been deprecated. Author message: The querystring API is considered Legacy. new code should use the URLSearchParams API ...
Read more >How to migrate from querystring to URLSearchParams in ...
URLSearchParams removes question mark character from the start of the URL query string. querystring keeps it and makes it part of the key...
Read more >Node.js Alternative after url.parse and querystring Deprecated
Since url.parse and querystring.parse is deprecated here and here at least since last LTS version 14. This one is the Web API standard....
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
after doing an npm update on my project laravel 9.11 and laravel mix 6.0.43 the same warning…
same problem