Use native Node URL parsing after Node 7.2.1 errors resolved

[ebidel]

I'm getting URL parsing errors in audits/dobetterweb/uses-http2.js that weren't present before #997.

When running:

npm run fast -- --output=html --output-path=results.html http://www.univision.com

Think it's failing on http://5321212.fls.doubleclick.net/activityi;src=5321212;type=unvsn_un;cat=unvsn_uv;ord=7762287885264.98?

[ebidel]

@wardpeet you mind investigating?

Also happening on https://www.healthcare.gov. The url that it is upset about is https://166688199.log.optimizely.com/event?a=166688199&d=166688199&y=true&src=js&s171652904=false&s171674651=none&s171946972=gc&s172159083=direct&s2417020537=true&tsent=1482274480.426&n=https%3A%2F%2Fwww.healthcare.gov%2F&u=oeu1482274480406r0.6877701290450859&wxhr=true&time=1482274480.425&f=7763110370,8016731066,7884071307,8073890089,7980150122,7763860875,7767800396,4681340685,7162490510,7975554292,7989202617,7768580538,8072450782&g=2177170222,2435330307&cx2=95f459d8

[Janpot]

Coincidentally I ran into this issue too a few days ago: nodejs/node#10306
a fix is on the way but updating the tests revealed more issues: nodejs/node#10317

[ebidel]

Thanks @Janpot. Looks like a Node issue. I'm also using 7.2.1

[wardpeet]

@ebidel I could use whatwg instead of url for node 7 until it is fixed
Ah looks like @brendankenny already did this :)

[wardpeet]

closing this one, fixed by #1187

[brendankenny]

I actually wanted to leave this open since we want to turn back on native node URL parsing when they fix their code. Changing the issue title to match that.

[paulirish]

k. The compliance issues that Jan pointed out earlier have landed in v7.4.0, which shipped yesterday.

Shall we add a "Compat:" comment indicating we can retire the whatwg-url module when < 7.4.0 is unsupported?
It will be many months, so I'd prefer that as our TODO rather than keeping this issue open. :)

[wardpeet]

good for me! :)
we might even do a version check in the file to use url when node > 7.4