URL() constructor

[onlywei]

Hello,

Are there any plans to add the URL constructor to this library?
https://developer.mozilla.org/en-US/docs/Web/API/URL/URL

Thanks.

[zloirock]

Thanks for proposal, I will think about it.

[zloirock]

I think, it's possible to add minimalistic implementation like that: https://gist.github.com/Yaffle/1088850

[zloirock]

In #288 proposed an option.

[zloirock]

Now it's an ECMAScript proposal, https://github.com/jasnell/proposal-url.

[KevinSnyderCodes]

jsdom implemented the URL class to the WHATWG standard: https://github.com/jsdom/whatwg-url

Would you be OK with using their code and formatting it to match the structure of your project? They also use the MIT license.

[kof]

what about using something like this as a polyfill?

import pick from 'lodash/object/pick'
import mapValues from 'lodash/object/mapValues'

const parser = document.createElement('a')

const components = [
  'hash', 'host', 'hostname', 'href', 'pathname', 'port', 'protocol', 'search'
]

export default function parse(url) {
  parser.href = encodeURI(url)
  return mapValues(pick(parser, components), decodeURIComponent)
}

[zloirock]

@kof at least, document.createElement('a') is not available in non-browser engines.

[zloirock]

@KevinSnyderCodes feel free to add it after merging v3 branch with master.

[yvele]

Is this issue also covering URLSearchParams polyfill?

Note that 2 polyfills already exists

• https://github.com/WebReflection/url-search-params (super popular)
• https://github.com/lifaon74/url-polyfill (less popular)

[zloirock]

@yvele yes, includes.

[zloirock]

Most likely, it will be added soon. I'm working on it.

[loganfsmyth]

@zloirock Would this be on by default, or opt in? I wouldn't want users of babel-polyfill to load this I don't think, at least not without opting in.

[zloirock]

@loganfsmyth it will be available in namespaces core-js/web and core-js/stage/0. Sure, in the main entry point too, but babel-polyfill don't use it.

[zloirock]

Available in core-js@3.0.0-beta.5.