From 05e5e8168e2c92ea6494e3964b5ceb6fadf7b96c Mon Sep 17 00:00:00 2001 From: James M Snell Date: Mon, 25 Jul 2016 10:10:39 -0700 Subject: [PATCH] Update proposal --- XXX-url.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/XXX-url.md b/XXX-url.md index b04f44d..ae0c3e6 100644 --- a/XXX-url.md +++ b/XXX-url.md @@ -14,17 +14,18 @@ the URL standard and fails to pass 160 of the WHATWG URL parsing tests. This proposal is to implement the WHATWG URL Standard by modifying the existing `url` module to provide an implementation of the `URL` object and associated APIs. Doing so improves the robustness of URL parsing, provides consistency -with browser js code, and can eventually allow the reduction of node.js specific +with browser JS code, and can eventually allow the reduction of node.js specific APIs. -Initially, the implementation would be introduced as an undocumented -experimental feature exposed via a new `URL` property in the `url` module. +Initially, the implementation would be introduced as an *undocumented* +experimental feature exposed via a new `URL` property in the `url` module +*and as a global*. Because the existing `require('url')` module remains, there should be no -backwards compatibility concerns. Once a decision is made to provide official, -documented support for the new URL implementation, a decision would be made -about whether to switch the internal uses of `require('url').parse()` to the -new `URL` implementation. +backwards compatibility concerns. Once the performance of the new URL impl is +on par with the existing `url.parse()` implementation, `url.parse()` will go +through a normal deprecation cycle and the new URL implementation will become +a fully documentation and supported feature. The current implementation can be found at: