-
Notifications
You must be signed in to change notification settings - Fork 525
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
fix(dependencies): replace qs by neoqs #6291
base: master
Are you sure you want to change the base?
Conversation
neoqs is API-compatible with qs in the legacy mode, and thus this isn't a breaking change. Of course if someone was already using qs and relying on it being deduplicated with the InstantSearch version. URLs parsed and created by qs and neoqs are compatible
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 9f92e8c:
|
Hmm bundle size is larger, doesn't seem to be due to non-working deduplication, maybe other features added since [email protected]? cc @puruvjdev is this expected? |
@@ -11,7 +11,7 @@ | |||
"algoliasearch": "4.23.2", | |||
"core-js": "2", | |||
"instantsearch.css": "8.3.0", | |||
"qs": "6.9.7", | |||
"neoqs": "6.2.12", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be 6.12.3, I released slightly wrong version.
I am looking at bundlephobia to see if that's the case, but it seems to be down. I'll let you know if that's the case. EDIT: well, its after 6.9.7 only that the library went crazy |
Well the real thing is that Only way the size would go down is by using the default build, which is ESM-only. I'd suggest using neoqs/legacy now with the extra 1KB, if it's not too much, but whenever in future you decide to drop CJS support, switch to Lemme know if that helps. |
Any update on this? 😁 |
Summary
Replace qs by neoqs. This doesn't have a bundlesize change, but it avoids us ever accidentally updating qs and having a big bump
Result
neoqs is API-compatible with qs in the legacy mode, and thus this isn't a breaking change. Of course if someone was already using qs and relying on it being deduplicated with the InstantSearch version.
URLs parsed and created by qs and neoqs are compatible