If you want to use this polyfill on older browsers we need to change the way to access at some properties that are reserved word, unfortunately.

I fixed it on my local branch, so I will propose a pull request on this issue.

Eg.
on modern browser = a.delete
on older browser (eg. Safari 5.0.3) = a['delete']

Would be nice to register this in the bower registry so we could bower install --save url-search-params. As far as I'm aware that package name is still available.

If use webpack entry built, it does not write variables on the window?

worked in Edge but not IE11

Add polyfill for URLSearchParams API

As the polyfill uses 'use strict', it fails to assign value to
URLSearchParams in url-search-params.node.js#L174, because it is not allowed to implicitly create global variables in strict mode.

On versions of Firefox from 29 to 43, there is partial support for URLSearchParams, but not complete support. The result for us is that when using this polyfill our site works on Firefox 28 and before, and 44 and after, but not on the versions in between, due to the fact that the library falls back to the browser version if it exists. For these cases, it would be nice to have a way to import this and override the browser implementation, rather than falling back.

https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams#Browser_compatibility

please add checking like : isSupportObjectConstructor = nativeURLSearchParams && (new nativeURLSearchParams({a: 1})).toString() === 'a=1'

Hi. I found a flaw in your project. I was able to fix it, but I can not build the project on my computer. What do I need to do before sending the PR?

Sorry for my bad english.

Firefox also implements a .searchParams property on anchors; demo. Maybe you can polyfill that via a HTMLAnchorElement.prototype.searchParams getter.

Btw, I wasn’t able to find in the URL spec where it says that anchors implement that API.

In Edge 41.16299.371.0, the polyfill seems to not create the global URLSearchParams object.

"URLSearchParams is not defined"

In Edge 42.17134.1.0 the problem does not occur.

In Edge 41.16299.371.0, the polyfill seems to not create the global URLSearchParams object.

"URLSearchParams is not defined"

In Edge 42.17134.1.0 the problem does not occur.

Hi
I am a member of CDNJS and in charge of adding this library to our CDN.
Could you please tell me which files do we need to let the library run on browser well?
Is url-search-params.js enough?
Thanks! 😄

The method is defined in the spec here: https://url.spec.whatwg.org/#interface-urlsearchparams

The sort() method, when invoked, must run these steps:

Sort all name-value pairs, if any, by their names. Sorting must be done by comparison of code units. The relative order between name-value pairs with equal names must be preserved.

Run the update steps.

The method is currently missing.

URL.prototype pretty much reflects HTMLAnchorElement.prototype on web platform, so, as a continuation of #1, FF implements not only HTMLAnchorElement.prototype.searchParams but also URL.prototype.searchParams, and I beleive this polyfill should shim it as well.

After updating to v0.10.1 I get:

import URLSearchParams from "url-search-params";
console.log(URLSearchParams);
// outputs: {}

@, etc

Some browser older versions include basic support for URLSearchParams but lack advanced features such as constructor USVString or init object support.

e.g. in Firefox v52 record as init object is not supported, but there is a native URLSearchParams constructor. This results in the polyfill not being used, but also the native implementation not working as intended.

Hi guys, unfortunately our shop (https://www.mytoys.de/) got an error after the last update 1 hour ago.

it seems that your last commit
14631ef#diff-b9cfc7f2cdf78a7f4b91a753d10865a2

results in an error that the constructor is not found, in our case it was like this

var URLSearchParams = require('url-search-params');
module.exports = {
var currentQuery = new URLSearchParams(window.location.search.length > 0 ? window.location.search.substr(1) : '');

JS-ERROR in Browser console: URLSearchParams is not a constructor

I think you couldn't see the side effects of your commit in package.json, but hopefully our feedback can help you to fix the bug in latest version 0.10.1

Greetings from Berlin

The native implementation of URLSearchParams is able to consume a FormData object as a constructor parameter, like:

const formData = new FormData();
formData.append('some-key', 'some-value');
const body = new URLSearchParamsConstructor(formData).toString();

I suggest doing a type check. And use FormData as it is supported.

const formDataToObject = (formData) => {
  const object = {};
  formData.forEach((value, key) => {
    object[key] = value;
  });
  return object;
};

function URLSearchParams(query) {
  if (typeof FormData !== 'undefined' && FormData.prototype.forEach) {
    if (query === instanceOf(FormData)) {
      formData = formDataToObject(formData)
    }
  }
 // etc

Is there a way to do this via an ES6 import? e.g.

import 'url-search-params'
// Expect window.URLSearchParams to exist

Are we plan support umd?
and support webpack and babel?
seems we should add module field in package.json.

after installing bower package, my build tool will include main file automatically, which is "build/url-search-params.node.js". however an error is thrown in browser:
Uncaught ReferenceError: module is not defined

main file for browser should be "build/url-search-params.js"

Typically fails on safari/webkit.
You will have much better luck replacing window.URL by a custom URL that inherits and overrides
the native URL implementation.

When importing as
import URLSearchParams from 'url-search-params'
and using it further in the code as
const urlParams = new URLSearchParams(window.location.search)
I get the following error:
TypeError: _urlSearchParams2.default is not a constructor
This started after the version update from 0.10.0 -> 0.10.1

In the URLSearchParams spec, the constructor supports empty arguments, a string, a sequence (e.g. array), or a record (e.g. object).

This implementation only supports the first two forms.

This should either be implemented or clearly documented as unsupported. Currently the README links to the MDN documentation which also lists all these constructor signatures.

I could take a stab at a PR if it would be accepted.

Edit: Using the latest v0.6 :)

is missing

new URLSearchParams('q=%2B').get('q') should return +(iOS 11 or Chrome or else), but it returns space ( ) on iOS Safari 10.3. It caused a bug on my project.

iOS Safari 10.3 support URLSearchParams however with this bug. I know it's not url-search-params' issue but it is a issue when i'm using URLSearchParams.

I resolved this by add string replace with + after I get q (see above). It's tricky.

Any idea to resolve this issue gracefully?

Thanks.

Hi,

I can t get it working in phantomjs.

It appears URL.prototype.search is not set, so at that line, the test won t jump in and the upgrade won t occur.

I m a bit loss in this prototype thing upgrade. Can you suggest something ?

thanks !