Repository navigation
Backport WHATWG URL to 6.x? #208
Description
Now that the WHATWG URL implementation is close to graduating from Experimental status, I would like to open a discussion about whether it makes sense to backport the implementation to 6.x..
/cc @targos @TimothyGu @watilde @joyeecheung @nodejs/lts
Activity
TimothyGu commentedon Apr 28, 2017
New features don't seem to be covered by the range of accepted changes in the LTS Plan…
jasnell commentedon Apr 28, 2017
They can on a case by case basis during the Active LTS phase.
TimothyGu commentedon Apr 28, 2017
Okay, rules notwithstanding personally I think it is a great addition. As a maintainer of node-fetch, the availability of a high-performance standard-compliant URL parser in all supported Node.js versions would be a boon for tricky bugs like node-fetch/node-fetch#245.
MylesBorins commentedon Apr 28, 2017
joyeecheung commentedon Apr 28, 2017
Can't see any harm in the idea...so +1
gibfahn commentedon Apr 28, 2017
+1, seems reasonable once it's graduated.
targos commentedon Apr 28, 2017
SGTM
watilde commentedon Apr 28, 2017
Sounds good to me as well.
sam-github commentedon Apr 28, 2017
+1 once not experimental
kumar303 commentedon Sep 14, 2017
It looks like it's graduated from experimental status now, right? nodejs/node#12710
jasnell commentedon Sep 14, 2017
Yes. It's no longer experimental
gibfahn commentedon Sep 16, 2017
This has plenty of +1s, so I guess it's just waiting for someone to raise a backport PR.
TimothyGu commentedon Nov 28, 2017
Backport PR: nodejs/node#17365
mhdawson commentedon Nov 28, 2017
+1 from me as well.
MylesBorins commentedon Feb 10, 2018
Coming out in 6.13.0