url-search-params | Npm Package Usage Trend

url-search-params

Simple polyfill for URLSearchParams standard

🌟 在 url-search-params 的 README.md 中顯示即時使用量圖表，只需複製下面的代碼。

## Usage Trend
[![Usage Trend of url-search-params](https://npm-compare.com/img/npm-trend/THREE_YEARS/url-search-params.png)](https://npm-compare.com/url-search-params#timeRange=THREE_YEARS)

🌟 在 url-search-params 的 README.md 中顯示 GitHub stars 趨勢圖表，只需複製下面的代碼。

## GitHub Stars Trend
[![GitHub Stars Trend of url-search-params](https://npm-compare.com/img/github-trend/url-search-params.png)](https://npm-compare.com/url-search-params)

套件	下載數	Stars	大小	Issues	發布時間	許可

url-search-params	105,236	763	-	0	7 年前	MIT

url-search-params

This is a polyfill for the URLSearchParams API.

It is possible to simply include build/url-search-params.js or grab it via npm.

npm install url-search-params

The function is exported directly.

var URLSearchParams = require('url-search-params');

MIT Style License

iOS 10 + other platforms bug

In case you'd like to replace the broken global native constructor, you can check some well known issue before including this polyfill on your project/page.

<script>
try { if (new URLSearchParams('q=%2B').get('q') !== '+') throw {}; }
catch (error) {
  window.URLSearchParams = void 0;
  document.write('<script src="/js/url-search-params.js"><'+'/script>');
}
</script>

About HTMLAnchorElement.prototype.searchParams

This property is already implemented in Firefox and polyfilled here only for browsers that exposes getters and setters through the HTMLAnchorElement.prototype.

In order to know if such property is supported, you must do the check as such:

if ('searchParams' in HTMLAnchorElement.prototype) {
  // polyfill for <a> links supported
}

If you do this check instead:

if (HTMLAnchorElement.prototype.searchParams) {
  // throws a TypeError
}

this polyfill will reflect native behavior, throwing a type error due access to a property in a non instance of HTMLAnchorElement.

Nothing new to learn here, just a reminder.