deprecate url module

[stevenvachon]

in favour of a global.URL, which could be whatwg-url.

Obviously, this would be a major version thing (7.0?).

[evanlucas]

I don't believe any more breaking changes can go into v7 at this point. The whatwg-url is also experimental.

[stevenvachon]

I'm fine with this being an 8.0 thing. I'm more concerned with it being a thing.

[claudiorodriguez]

Don't really like the global approach. Deprecating (if necessary) the url lib api in favour of what was introduced in #7448, maybe.

[stevenvachon]

It uses more memory, I guess, but it simulates window.URL.

[jasnell]

the new URL implementation is still experimental and will be through at least v8.0. The earliest we could consider deprecating url.parse() would be v9.0 and it would be much much longer before we could remove or replace it. The CTC decided against making the new URL class a global, which means that TC-39 would need to make it a global in the language in order for it to become a global in Node.js. Later on, once the implementation is no longer experimental, we could revisit that decision but for now, that's how it stands. The url module itself will not be deprecated at any point in the near future.

[stevenvachon]

Ok. What is the CTC, by the way? Do you mean ECMA?

[jasnell]

Sorry, CTC == Node.js Core Technical Committee.

[stevenvachon]

Is there a URL global proposal? I don't see one at https://github.com/tc39/proposals

[jasnell]

tc39/proposals#30

[stevenvachon]

wtfux! Thank you.