Make it possible to use parse5 as optional(?) parser

[inikulin]

Today I'm deprecating whacko, so, if cheerio maintainers don't mind, I'll send those who is interested in this feature here.

[fb55]

@inikulin Would you mind sending a PR? As I haven't worked on htmlparser2 for a long while, it is probably better to drop it entirely.

[inikulin]

Would you mind sending a PR?

Sure. Unfortunately, I'm quite busy at the moment, however I believe I'll be able to get my hands on it somewhere at the end of the month.

[dypsilon]

Hi, what is the status on this? It would be huge improvement.

[inikulin]

@dypsilon Currently I'm extremely busy. As soon as I'm done with my job duties (I hope at the mid-August) I will start working on this one. Meanwhile, PRs are welcome if someone else would like to start work on this.

[stevenvachon]

If htmlparser2 is removed, what will be used to parse XML? sax?

[fb55]

You will still be able to modify htmlparser2 dom stuctures, so you might have to parse xml in a separate step (one additional line).

[stevenvachon]

@fb55 but which tool will/should be used in that separate step?

[fb55]

htmlparser2 directly :)

[stevenvachon]

Ok, so then cheerio will lose the ability to parse XML out-of-the-box.

Perhaps an XML-only fork of htmlparser2 is on the distant horizon?

[luanmuniz]

parse5 will parse xml as well. Its what whacko is using

[stevenvachon]

@luanmuniz XML is case-sensitive, HTML is not.

[luanmuniz]

@stevenvachon https://github.com/inikulin/parse5
It parse xml as well

@fb55 i would like todo this. I'm sing whacko for a long time and since its not supported anymore. I would like to make cheerio use parse5. Can you give me some instructions and points that i need to pay attention when i'm working on this?