-
Notifications
You must be signed in to change notification settings - Fork 89
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
How is this different from other polyfills? #2
Comments
To answer my own question, it looks like the main difference is that this is a polyfill, vs. url-search-params is a ponyfill. Is that accurate? |
Yes, you are right. First I wrote this library because there is no suitable to choose. The main difference I think is that, url-search-params is more like a library that for nodejs only. Although they support AMD and UMD libraries, but you cannot use it for webpack or other package scenes. This library is more emphasis on the browser side, of cause, can also be used for Nodejs . It will register a global var for You can use this for all the browser scenes or with other libraries, such as whatwg-fetch. Whatwg-fetch will depend on URLSeatchParams class in some scenes, but you cannot use the other library instead. Of course I also consider merging this library into another. 😃 |
Cool, thanks for the explanation! |
I thought that my bad English would make you doubt, fortunately, did not 😂 |
Specifically, what are the differences between this library and https://github.com/WebReflection/url-search-params, which seems to be recommended by google here: https://developers.google.com/web/updates/2016/01/urlsearchparams. Can you explain a little bit about how this polyfill is different?
The text was updated successfully, but these errors were encountered: