url-search-params
Simple polyfill for URLSearchParams standard

url-search-params downloads url-search-params version url-search-params license

url-search-params유사 패키지:
npm 다운로드 트렌드
3 년
🌟 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)
Cumulative GitHub Star Trend
🌟 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-params105,236763-07年前MIT
url-search-params의 README

url-search-params

build status CDNJS version donate

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.