Steven Vachon

Currently, no. PR welcome, though.

Leaving this open until it's correctly fixed.

Sure, whatever works. This project will have a lot of major changes in 8.x and more after. It's a deep rabbit hole.

Can you provide the HTML that caused the issue?

``` js var result = require("parse5").parse("text", {locationInfo:true}); console.log(result.childNodes[0].childNodes[1].childNodes[0]) ``` produces: ``` js { nodeName: 'a', tagName: 'a', attrs: [ { name: 'href', value: 'test' } ], namespaceURI: 'http://www.w3.org/1999/xhtml', childNodes: [],...

Indeed. I haven't started solving it yet, but it would need to be a dependency so that accurate location info can be provided. The goal is to provide the tools...

v0.8 will likely have JSON log output. Perhaps a flat URL list could be an option.

A 3xx redirect to where? If it results in a 200, then it was a successful redirect, not a broken route.

Ok, but it's not "broken" as it has a successful redirect. Not sure what to call it.

While a color is good for a UI, I don't think that it's the right word for data.